> > Personally, I'm noticing a lot of requests for XML namespace selection
> in
> > the parser. Can we get that into 1.1? Apperently, making $('myns:div')
> > would raise holy hell because it would clash with the pseudos, but
> > $('myns|div') might be doable.
>
> +1 for namespace selection.
>
> In one of my current projects, we added custom attributes to form
> elements to use them as widgets.
>
> As jQuery doesn't allow this kind of selection, we were forced to
> invalidate our XHTML. God killed a kitty.
>
> I wouldn't like to do it again.
No need to harm any more kitten while avoiding namespaces: Take a look at the
metadata plugin, it promotes valid markup without namespaces.
You are free to choose from three types of metadata: "class" (now default),
"attr" and "elem".
For example, when using the default "class", you'd write your metadata this way:
<tag class="some styles {data: "123",x:[1,2,3]}" />
Inside the brackets any javascript syntax is valid. By using types attr or
elem, you can specify the same data in different places: attr uses custom
(invalid) attributes, elem extra elements (eg. script).
--
Jörn Zaefferer
http://bassistance.de
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
