Re: [whatwg] Arbitrary HTML in option-elements
On Tue, 30 Nov 2004, Matthew Raymond wrote: Olav Junker Kjær wrote: It would be a useful feature if arbitrary HTML was allowed in option elements. E.g. items in a dropdown could have different icons. Yeah, personally, I think we should look at adding the |icon| attribute to the option element. We can't allow arbitrary markup in option in text/html for legacy reasons. The icon idea seems reasonable for menus of actions, but we're doing with with menu now; for drop down lists, most lists in most operating system UIs don't seem to have an icon so I'm not convinced we really want to expose that yet. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Arbitrary HTML in option-elements
On Tue, 30 Nov 2004, Olav Junker Kjær wrote: Generally, I think its a very good thing that the spec tries to define how to handle invalid HTML. Undefined and optional behavior in interpreting HTML is bad thing IMHO. Maybe the rules for parsing invalid HTML (in HTML5) could be generalized, something like: [...] Since we now have very specific parsing rules, this probably no longer really applies. Please let me know if you disagree with what the spec says today about handling invalid HTML (and option elements in particular). -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
