I always found styleId confusing also. But for myFaces it can't be id, it has to be something else, so styleId makes sense. This is a fantastic idea.
Also, implementing the <p> tag and the <div> tag are great ideas as well.
Thanks all,
Ray
Sean Schofield <[EMAIL PROTECTED]> wrote:
Sean Schofield <[EMAIL PROTECTED]> wrote:
> No, it is only used for uniqueness on the client-side. Component tree
> doesn't require unique id's. Id's must only be unique beneath a given
> NamingContainer.
So if MyFaces were to continue to generate this guaranteed unique id
by default it would still be observing the spec right? This would
just give the user the option to specify their own id if they didn't
care or wanted to handle the uniqueness themselves. I am right here?
Also, styleId would be more familiar to Struts users although
personally I always found the use of the name confusing.
sean
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
