users@javaserverfaces-spec-public.java.net

[jsr344-experts mirror] Re: HTML5 friendly markup (fix inconsistencies and documentation review)

From: Leonardo Uribe <lu4242_at_gmail.com>
Date: Sun, 4 May 2014 18:53:14 +0200

Hi

FC> Your proposed change reflects the current (intended) behavior. Though it can
FC> be achieved by changing just 2 words (bold):
FC>
FC> * If the current attribute's namespace is not empty and different from the
FC>
FC> argument tag's namespace, let the current attribute be
FC> convertedTagAttribute. This will have the effect of setting the current
FC> attribute as an attribute on the attributes map of the UIComponent
FC> instance represented by this markup.
FC>

Yes, it is the same meaning. But please note in some cases this behavior is not
desired, because as mentioned before, there are cases where you want to render
the attribute with namespace as passthrough, not just add it into the component
attribute map. Of course it is not a very common case, but it sounds like
something good. I was thinking on add this as an implementation
specific compiler
flag. But is a rare case, maybe we should not bother by that, anyway I
just wanted
to mention the possibility that in the future we could need to change
these lines
again.

FC> I like this simple rule: Empty namespace always makes it into the
FC> passthrough attributes and these always take precedence.
FC>
FC>
FC> Yes, we should add style and styleClass.

Ok.

regards,

Leonardo Uribe

>
> Ciao Frank