- From: Philip Jägenstedt <philipj@opera.com>
- Date: Fri, 15 Jan 2010 18:05:09 +0100
- To: "Toby Inkster" <tai@g5n.co.uk>, "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>
- Cc: "public-html@w3.org" <public-html@w3.org>
On Fri, 15 Jan 2010 17:13:43 +0100, Toby Inkster <tai@g5n.co.uk> wrote: > Philip Jägenstedt wrote: > >> I don't think this is a very good idea, as data-* are always hidden >> and not suitable for marking up content that is visible in the page. > > You are mistaking my proposal for a method of embedding data into a > document. The proposal is not intended for embedding the kind of data > that Microdata or RDFa embed; rather it's a general purpose extension > point that other standards ("otherspecs") could use. Yes, I did assume as much from the examples, but in fact I think they are effectively the same thing. Only user agents can change the behavior of any element/attribute in other ways than what is already possible using JavaScript and CSS. If you are a user agent (especially a browser) then I would argue that you *shouldn't* be making stuff up, you should make a proof-of-concept and then propose the feature for standardization as a proper HTML feature. Centralization here is a good thing, because it makes vendors talk to each other and improve the feature before it is too late. If, on the other hand, you are not a user agent, then the only thing you can do is embed data and make any behavior/rendering with JavaScript/CSS. For embedding the data/hooks you need you can use data-* attributes, clasa attributes, microdata or whatever you want. -- Philip Jägenstedt Core Developer Opera Software
Received on Friday, 15 January 2010 17:17:12 UTC