Current codebase renders different output for read-only inputText and
read-only selectOneChoice as I think they would be same.
tr:selectOneChoice renders only spans with value between,
tr:inputText renders spandivvalue/divspan.
Probably all non-elements outputs (which call
Method FormInputRenderer.renderRootDomElementStyles renderes styleClass
as first followed with styles from skin. I think styleClass should be
the last one because common scenario uses skins and in special cases
user overrides style in JSP with styleClass attribute.
In my case is it style
Hello Martin,
I thought it worked that way before as well, however it's not the issue. The
style that will get the highest priority will be the last one defined in the
generated CSS not in the html element's class list. The order of the
selectors within the generated CSS is not really easy to
Thanks Adam, I realized that after sending this initial email, and now I
have no need to get all the icons because I plan to go a different route
to getting the icons to the client, so I am not planning to implement
this api now.
- Jeanne
Adam Winer wrote:
getIcons() makes sense. But
Hi Adam,
I used YMajorGridLineCount, YMinorGridLineCount and XMajorGridLine count. I
made a path with all the changes recommeded by you and submitted a path this
morning.
Thanks,
Venkata
On 9/20/06, Adam Winer [EMAIL PROTECTED] wrote:
I think it's good getting Grid in there, dunno about
Hi Joey,
I haven't had time to respond.
I don't know what the dependency method should be.
Your suggestion:
Is it acceptable to locally apply the earlier patch that has not yet
been committed and, in effect, include that patch in a new patch?
I think this is acceptable, because I don't think
I have a question regarding pda code.
In Faces Major renderers, do we add pda hooks into the renderer, or
should we have separate pda renderers?
I was looking at the pda patch for autoSubmit, and I see this code in
FormRenderer. Do we have a rule as to when we
should use a pda renderer instead
