- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 11 Dec 2006 20:55:32 +0000 (UTC)
On Mon, 11 Dec 2006, Alexey Feldgendler wrote: > On Mon, 11 Dec 2006 06:25:27 +0600, Ian Hickson <ian at hixie.ch> wrote: > >> > >> 1.) Inserting Sam Ruby's SVG logo into HTML, for one example. > > > > The <img> element already supports images in HTML. You can even embed > > images directly in the page with data: URIs, regardless of the format > > (be it PNG, JPEG, or SVG, for example.) > > You won't be able to manipulate the SVG DOM in this case. Your use case didn't mention manipulating the DOM. Moving targets are hard to hit -- that's why we try to list the use cases before designing the solution. > >>> We already have such a mechanism, namely, plugins. > >> > >> Two extension mechanisms are not possible? > > > > Redundancy is always possible. Whether it is desireable is the > > question. > > These are actually two independent aspects: > > 1. Native support vs. plugins. > 2. External resources vs. inline data. > > Native support + external resources --> e.g. JPEG <img href="http://..."> > Plugins + external resources --> e.g. Flash > Native support + inline data --> e.g. JPEG <img href="data:..."> > Plugins + inline data --> no examples yet, but why not? "Why not" is not a design process, sorry. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 11 December 2006 12:55:32 UTC