CSS also allows character escaping:
#user\\.name { }
But guess which browser doesn't support that? In IE you'd have to use
a hex code: #user\2e name { }
On May 26, 5:21 pm, MorningZ <morni...@gmail.com> wrote:
> So if you had:
>
> <input type="text" id="user.name" />
>
> how would you apply a style to that?
>
> can't say:
>
> #user.name {
>
> }
>
> because that would look for
>
> <input type="text" id="user" class="name" />
>
> yeah, "poor choice" sure is relative, but why make things more
> difficult, when a simple dash or underscore would do the same thing
> (and not cause issues with basic CSS or jQuery)
>
> On May 26, 3:03 pm, Ricardo <ricardob...@gmail.com> wrote:
>
> > "Poor choices" is relative. I'd love a way to use colons in IDs
> > avoiding the confusion with pseudo-selectors, kind of like namespacing
> > elements. If it's in the specs it's perfectly valid.
>
> > On May 26, 9:17 am, MorningZ <morni...@gmail.com> wrote:
>
> > > No, it's not a bug, your selector is looking for an item of class
> > > "name"... so it's your selector that is the issue, not jQuery (your
> > > naming/id convention would also cause issues with CSS)...
>
> > > If you insist on poor choices for naming your controls, it is still
> > > possible to select the items though
>
> > >http://docs.jquery.com/Frequently_Asked_Questions#How_do_I_select_an_...
>
> > > On May 26, 4:09 am, "weit...@263.net" <weit...@263.net> wrote:
>
> > > > when i use jquery get a input like
> > > > <input type="text" id="user.name" name="user.name"/>
>
> > > > use $("#user.name") is error
>
> > > > if input is
> > > > <input type="text" id="username" name="username"/>
> > > > use $("#username") is right
>
> > > > is bug?
