- From: Dao Gottwald <dao@design-noir.de>
- Date: Thu, 29 Mar 2007 17:32:12 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: public-html@w3.org
In order to avoid having to mess with a bunch of related attributes as with "href", I'd allow "src" (or "data"?) and "type" only. I'd see it as a <object> shorthand, thus it should behave the same when it comes to events. Note that by "every element", I mean those who can have visible child nodes. This way you automatically exclude elements that have a src attribute today. That's all a bit tricky though, as it implies inconsistencies. E.g. <img src="foo.png" alt="foo"> would differ from <span src="foo.png">foo</span> in some non-obvious ways. --Dao Anne van Kesteren wrote: > > On Wed, 28 Mar 2007 18:29:21 +0200, Dao Gottwald <dao@design-noir.de> > wrote: >> .... which seems very plausible to me. Contrary to letting every >> element have a href attribute, it's backwards-compatible by design. > > Not really. <script src> has very different semantics from <img src>, > <iframe src> and <embed src> for instance which have different semantics > from <video src>, <event-source src> and <source src> (which also all > differ from each other). The semantics of an element are in general > decided by the element and after that by their attributes. This means > that how the attribute functions depends on the element and not the > other way around. > > Exactly the same arguments as for href="" apply I would say. For src="" > you have can think about how loading would happen for the element. When > are the various events dispatched? Does the element delay the load event > of the document? Does it start loading the monment it is inserted? Does > mutating the src="" attribute affect any API (see <event-source>)? Et > cetera. > >
Received on Thursday, 29 March 2007 15:32:17 UTC