I agree that a spec is a spec. The problem is rigidly adhering to it will break to rest of the specs that work along side the html specs to produce the intended result in the presentation layer. I too had to change the way I assigned id's to accommodate css and js that used css selectors. If anyone wants to use periods, they should feel free, but I doubt the css and javascript communities will feel obligated to accommodate them. No offense meant whatsoever, I had the same issue.
On Fri, Oct 17, 2008 at 2:55 PM, Jeffrey Kretz <[EMAIL PROTECTED]>wrote: > > It's not useful to claim that the specs are faulty. Until they change, > dots > in IDs are legal and valid. > > JK > > -----Original Message----- > From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of ricardobeat > Sent: Friday, October 17, 2008 10:21 AM > To: jQuery (English) > Subject: [jQuery] Re: dot separated id > > > Yeah, that's a fault in the specs. XHTML specs also allow dots in IDs: > > 'only strings matching the pattern [A-Za-z][A-Za-z0-9:_.-]* should be > used.' - http://www.w3.org/TR/xhtml1/#C_8 > > But that causes problems for CSS too: > > <div id="tom" class="cat"> > <div id="tom.cat"> > > #tom.cat { which one are you referring to? } > > - ricardo > > On Oct 16, 7:41 pm, "Mauricio \(Maujor\) Samy Silva" > <[EMAIL PROTECTED]> wrote: > > Specs at link pointed out says: > > ID and NAME tokens must begin with a letter ([A-Za-z]) and may be > followed > > by any number of letters, digits ([0-9]), hyphens ("-"), underscores > ("_"), > > colons (":"), and periods ("."). > > > > Aren't dots and periods the same? > > > > > > ---------------------------------------------------------------------------- > ----------------- > > > > double backslashes are the short term fix, but remember for the long > > term that dots are illegal in ID's and will cause your page to not > > validate. > > > > seehttp://www.w3.org/TR/html401/types.html#type-namefor reference. > > > > -micah > > -- Christopher Thatcher
