Hi
I also notice this error in the facelets taglibdoc of jsf:element :
"... Markup element that causes a component of component-type:
javax.faces.Panel with renderer-type: javax.faces.passthrough.Element
to be inserted in the tree. ..."
It should be like this:
"... Markup element that causes a component of component-family:
javax.faces.Panel with renderer-type: javax.faces.passthrough.Element
to be inserted in the tree. ..."
The component-type should be unique in the family. So, for the
component-family javax.faces.Panel, only UIPanel could have
component-type javax.faces.Panel and so on.
The renderer javadoc is correct:
component-family: javax.faces.Panel renderer-type:
javax.faces.passthrough.Element
the component type and class can be an implementation detail.
Also in the facelets javadoc there is a link:
p:_
with no documentation at all.
regards,
Leonardo Uribe
2013/1/30 Leonardo Uribe <lu4242_at_gmail.com>:
> Hi
>
> Checking the spec of TagDecorator, I notice that it could be a good idea allow
> the following syntax:
>
> <a jsf:outcome="..."> --> <h:link outcome="...">
>
> <button jsf:outcome="..." --> <h:button outcome="...">
>
> Since h:commandLink and h:commandButton does not have outcome property, there
> is no problem and it help simplify code writing.
>
> As another comment, according to the spec:
>
> <input type="email" ...>
>
> becomes:
>
> <h:inputText ...>
>
> but since the inputText Renderer doesn't know type property
> it renders this:
>
> <input type="text" ...
>
> The RenderKit javadoc of javax.faces.Input/javax.faces.Text must be changed
> to reflect that use case, and probably
> javax.faces.component.html.HtmlInputText must be changed too.
>
> I'll keep trying to find issues in the spec.
>
> regards
>
> Leonardo Uribe