I’ve updated my marketshare spreadsheet for June 2010 charting the percentage of web users who can view SVG and Canvas: 41.49%
Note that I added “Canvas” back into the title of these blog posts, now that it is public that IE9 is supporting the HTML5 <canvas> element. I’ve also added SVG-as-an-image (usable inside <img> or as a CSS background-image), since that’s something that seems likely to be supported soon by all browsers (Firefox 4, IE9).
P.S. This figure does not take into account any user that has a SVG plugin installed or authors who have used the excellent SVG Web or excanvas shims, so this is really a worst-case number.
P.S. I should mention that this figure does not take into account any user that has a SVG plugin installed or authors who have used the excellent SVG Web or ExplorerCanvas shims, so this is really a worst-case number.
Issue 70 has been open for awhile now. In fact it’s one of just a handful of two-digit bugs left in SVG-edit. Now that all browsers have heralded support for SVG into the future, one might argue that the need for this bug will evaporate in a couple years. However, one would be wrong. First, there are lots of mobile browsers out there. Second, in some cases it could be easier to just tell the browser how to draw a collection of dots rather than mathematical instructions (think thumbnails). So how to solve it? Read the rest of this entry …
Cameron Adams decided to benchmark Flash, SVG, Canvas and HTML5 using a particle engine he created. Not surprising (to me anyway), the SVG scores were the worst of the bunch. This stands to reason: does each particle really need to be a DOM element? Nonetheless, I decided to see what I could do to make the SVG scores suck less. I thought I’d use it as an opportunity to also teach some techniques. Read the rest of this entry …
P.S. I should mention that this figure does not take into account any user that has a SVG plugin installed or authors who have used the excellent SVG Web or ExplorerCanvas shims, so this is really a worst-case number.