[Bug 18863] [Custom]: Consider only restricting naming to contain a dash

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18863

--- Comment #6 from Daniel Buchner <danieljb2@gmail.com> ---
(In reply to comment #5)
> My $0.02
>  
> > 2. Do we really want to end up with this: <-sometag> or <sometag->, if not,
> > are we going to institute another restriction that the tag cannot begin or
> > end with a dash?
> 
> I'm of the mind that we don't need to worry about this. If some developer
> does this they will either have a good reason or they will be ridiculed.
> 
> > 3. Is namespacing for tag names really as much a concern as JS variables? I
> > would argue that it isn't, because 99% of the time you know what tags are
> > included in your app.
> 
> Does this not conflict with your argument #1?
> 
> In any case, I'm not sure what you mean. If YUI provides "x-button" and
> JQuery provides "x-button", there goes the lovely interoperation we seek.
> Almost certainly it will become standard to prefix your tags. Then we have
> alphabet soup.
> 
> > 4. is it really providing a significant value?
> 
> I know you need more opinions than just mine, but I still say yes.
> 
> S

One last, real concern: are we 100% sure we'll never have an HTML element
native to the spec that has dashes in it? If there was ever a natively-dashed
tag name, would this create a problem?

All in all, I'm not passionate about it - it's just another nit in the way of
landing the patch in Firefox and a odd way of inferring that an element has
super powers.

I'm punting to Dimitri :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 11 December 2012 00:05:47 UTC