- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 19 Oct 2009 14:53:23 -0500
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Shelley Powers <shelley.just@gmail.com>, James Graham <jgraham@opera.com>, Anne van Kesteren <annevk@opera.com>, Adrian Bateman <adrianba@microsoft.com>, Jonas Sicking <jonas@sicking.cc>, Tony Ross <tross@microsoft.com>, "public-html@w3.org" <public-html@w3.org>
On Mon, Oct 19, 2009 at 1:27 PM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > Tab Atkins Jr. On 09-10-19 19.11: >> I can't tell from searching around on the svgweb demos how it uses >> data-* attributes, but this really shouldn't be a problem in practice. > > From the SVGweb quick-start: > > ]]If your HTML page and the SVG Web library are in different directories, > you also must provide a data-path HTML 5 attribute pointing to where the SVG > Web files are.[[ > >> If svgweb uses data-svgweb-* attributes, frex, then the chance of >> clashing with another library is basically nil. Before starting any >> new library one should probably google for a bit to make sure that >> one's preferred name for the project isn't already being used. > > > @data-path seemed pretty generic. And in my mind (or in a code example I > Googled) they used it on <object>, which already has @data. Yeah, just using @data-path is a pretty bad practice. ;_; That's precisely the sort of thing that *will* lead to name clashes. Pretty much only authors using data-* for self-written scripts should ever use plain words like that - all libraries should definitely prefix their data-* attributes. ~TJ
Received on Monday, 19 October 2009 19:54:17 UTC