|
Could we not come up with our own standard for myfaces for the time
being? And hopefully the JCP will follow suit or at least make for an
easy transition. This is such an essential thing these days especially
with everyone seeing what Google is doing lately. Travis Matthias Wessendorf wrote: As far as I understand it, it should be addressed at JCP, isn't it? Since these guys define the standard for JSF.Regards, Matthias-----Original Message----- From: Martin Cooper [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 30, 2004 5:58 PM To: MyFaces Discussion; [EMAIL PROTECTED] Cc: Sean Schofield Subject: Re: _javascript_ getElementById Issues There needs to be a better way than that. Every decent _javascript_ library out there uses getElementById() to manipulate elements and allow people to build dynamic web apps. A "solution" that requires either wrapping every component usage in a proxy tag or overriding all of the components isn't tenable. People building dynamic web apps are not going to adopt JSF with those kinds of constraints imposed on them. I can see why there might be issues with components inside of something like a data grid. But this can be overcome by, for example, taking the id provided and adding an index using a well-defined scheme, so that other _javascript_ code can know how to identify the relevant elements. -- Martin Cooper On Thu, 30 Dec 2004, Heath Borders wrote: -- Travis Reeder Ecommstats Web Analytics www.ecommstats.com |
- Re: Javascript getElementById Issues Travis Reeder
- Re: Javascript getElementById Issues Sean Schofield
- Re: Javascript getElementById Issues Werner Punz
- Re: Javascript getElementById Issues Craig McClanahan
- Re: Javascript getElementById Issues Heath Borders
- Re: Javascript getElementById Issues Sean Schofield
- Re: Javascript getElementById Issues Craig McClanahan
- Re: Javascript getElementById Issue... Heath Borders
- Re: Javascript getElementById I... Ray Clark
- Re: Javascript getElementBy... Heath Borders
- Re: Javascript getElementBy... Sean Schofield

