Ganesh schrieb:
the second (enhance transport):
Why would you put <script>...</script> inside the attributes section?
The spec says it is used to >>update the DOM element attribute value
(whose name matches attribute name), with attribute value<<. I can't see
in which way this is connected to replacing scripts.
Script should never be in the attributes section, this is clearly an
eval block, sorry if I was unclear in this regard!
The attributes section is there to update attributes of tags/components
including the styles and styleClasses on dynamic level (and we have
a pretty well working implementation which took me a fair amount of
research to bypass all the browser quirks)
I was generally talking about this problem in the spec, attributes is
the area where we have clearly the same issue in mind, you on the client
side with auto eval of embedded css blocks, me with not being able
to trigger the attributes section in a clean and easy way by the
component authors (which was clearly ment to do the job on server side
level)
Anyway either way to become on topic dynamic styles on the client side
is a must, if it can be pulled off.
And there is no overlap in functionality. If a component author can pull
off to open the attributes tag(it still is possible but really messy)
then he can write to attributes directly on the server anyway including
dynamic styles)
otherwise our client side attributes can kick in.
