I think its called styleId because the html "id" attribute was originally used for CSS, not just to uniquely identify an element.
Yes, Myfaces would still be following the spec for the behavior of components if we did this. However, we could only do this on our extended component set, rather than the default set of components. This is because the components under the javax.faces.component.html package are part of the API, so we can't alter their behavior. For our components, we should probably say that if the user enters both an "id" and a "styleId" then we should throw an IllegalStateException since it would be a bit confusing which clientId should be generated (either the id's of all the parent namingContainers strung together + the id, or just the styleId). On Sat, 1 Jan 2005 12:18:21 -0500, 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 > -- -Heath Borders-Wing [EMAIL PROTECTED] On Sat, 1 Jan 2005 09:22:39 -0800 (PST), Ray Clark <[EMAIL PROTECTED]> wrote: > 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: > > > 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 -- -Heath Borders-Wing [EMAIL PROTECTED]
