There is one very, very valid reason for forceId I keep reiterating over and over (me not being a friend of forceId in the firstplace, but very happy to have it after doing some real world JSF-projects):
when you style with CSS, you quite often style with respect to the id - the # selector is what is used for this. Now, the JSF generated ids are looking like this: formId:namingContainerId:myComponentId if you use this in your CSS, the selector will become the following: #formId:namingContainerId:myComponentId now, the colon is also the pseudo-class selector in CSS (e.g. a:hover), and I have unsucessfully tried to get this type of selection to run in any current browser - id styling just doesn't work anymore with the JSF approach of designing id's, obviously. Please, please, correct me if I am wrong (I'd be very happy to be corrected regarding this)! regards, Martin On 1/7/06, Volker Weber <[EMAIL PROTECTED]> wrote: > > Volker Weber wrote: > > > > I think i should read this tread. > > > > [1] http://www.mail-archive.com/[email protected]/msg00680.html > > > > After reading this, i think there is only one new aspect for me. > > The problem with porting existing applications to jsf. If those existing > application uses javascript with *hardcoded* element ids, which can't be > easyly changed to the new naming sheme. > > This scenario is the only one where i'm (for me) willing to accept the > use of forceId. > > But i fear that the page structure is changing so mutch, when porting to > jsf, it will break those scipts anyway. > > Regards > Volker > > -- > Don't answer to From: address! > Mail to this account are droped if not recieved via mailinglist. > To contact me direct create the mail address by > concatenating my forename to my senders domain. > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
