Oh right, forceId! That allows me to clean up some of my code nicely.
Speaking of the "simple" example, I think they should use forceId more
often. e.g. in the panelNavigation2 example, adding forceId="true" to
the t:div's would make it much easier to get this example working in
one's own application - particularly when the developer isn't wide awake
or thinking about these id caveats! ;)
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Sean Schofield wrote:
This seems to work well, though one must be careful to account for the
resulting changes to the "id" attribute of all enclosed components. Note
that some of these components may be rendered inaccessible to CSS #
statements in IE, which does not recognize the \: escape sequence for
CSS.
That's why I created forceId. IMO the JSF EG did not take into
consideration all of the CSS and javascript that is not going to be
generated by the component. That's a big problem with JSF 1.1
although it appears to be partially addressed in JSF 1.2. Search the
archives for the older threads on forceId and also see the simple
examples.
Sean
