Have you tried "*[id='myForm:myName']"? That ought to work, though it wouldn't surprise me if it did not.
A colon is a valid character in ID attributes, so it should be supported. Part of me thinks that the attribute selector approach (if it works) would be sufficient -- but another part of me thinks we should follow jQuery's lead here and just special-case the double- escaped colon in all contexts. (Out of curiosity, what happens when you try to target #myForm:myText with a CSS selector? The use of the colon to denote pseudoclass would seem to be a problem in CSS as well.) Cheers, Andrew On Jul 11, 10:43 am, kangax <[EMAIL PROTECTED]> wrote: > I stumbled upon <a href='http://www.zachleat.com/web/2007/07/10/ > javascript-frameworks-and-jsf/'>this page</a> which compares how > various JS frameworks interpret ':' inside a CSS selector function. > I don't know if it's easy to implement, but would definitely be a good > addition (as of now only jQuery understands such syntax). > > Do you think it's worth adding something like that? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
