Hi Ed,
Am 11.07.2012 um 18:18 schrieb Edward Burns:
> SECTION: API Changes
The spec feels clear so far. But there remain some questions:
If Html5 gets a new element (like button for example) we can't support it out of the box because we have this mapping. I would like to give the developer a simple way to extend JsfPassthroughElementLibrary. Maybe we can have something like Application.addPassthroughElement(String tagName, String componentFamily, String rendererType).
How can we distinguish between <input type="text"> and <input type="submit"> (which have different decode behaviors), if the mapping relies only on the element name?
How do we handle select/option/optgroup (maybe
http://java.net/nonav/projects/javaserverfaces-spec-public/lists/users/archive/2012-06/message/43 helps)?
I'd like to have a wildcard mapping: For all non mapped element names, we create componentFamily javax.faces.Panel and rendererType javax.faces.passthrough.Element.
> SECTION: Implementation Changes
>
> M jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/ComponentRule.java
>
> - Modify LiteralAttributeMetadata to take the TagAttribute instance,
> rather than its value, in the ctor.
>
> - In LiteralAttributeMetadata.applyMetadata(), if the namespace of the
> tag for this attribute is <http://java.sun.com/jsf>, put the attribute
> in the pass through map. Otherwise, put the attribute in the
> attributes map.
Shouldn't it be the other way round?
Ciao Frank