Joerg Heinicke wrote:
Sylvain Wallez <sylvain <at> apache.org> writes:
Now the question is: do you find the \3A quirk to be a blocking issue?
It seems to me that more often inputs in a form will be styled using
classes, so as all inputs share the same styling rule. Also, a way to
avoid the quirk is to use the ancestor selector, which works in all
tested browsers:
#datasource\.SQL\.login input { background: #FF0000 }
Sorry to go back to the origin of this discussion, but wouldn't it then be
better to generate an id for the ajax wrapper element instead of the input
element? Nobody cares about the wrapper element, but nearly everybody about the
styling of the form and so the inputs. So giving them the id they have in the
form definition seems to be more than obvious.
So you suggest:
<span id="foo:container"><input name="foo" id="foo"></span> ?
Ajax cares *alot* about the container id, as it's the element that is
updated. If the container's id isn't the widget's full name, it means
we'll have to take into account this special naming for HTML rendering
of widgets everywhere
My impression (but that's only mine) is that access to individual inputs
is mostly needed from JS code (to plug some additional behaviour) rather
than from CSS (use classes to style globally rather than individually),
so the unicode escape quirk is should not really be an issue.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
