Hi Kito,
Ughh, as you pointed out the client id is already there. My brain just
stopped working :(.
However I still want to mark this issue as "Won't fix" as there is no
way of knowing how a specific component is being rendered and which HTML
element corresponds to the client id of the component. And no I don't
want to make any assumption on how it is structured.
Thoughts?
Manfred
On 1/12/15, 11:13 AM, Kito Mann wrote:
> Manfred, can you articulate your objection more clearly? We definitely
> know the client id before the JavaScript executes, since it executes
> on the client :-).
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
> http://www.JSFCentral.com | @jsfcentral
> +1 203-998-0403 <tel:%2B1%20203-998-0403>
>
> * Listen to the Enterprise Java Newscast: _http://
> <http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com
> <http://ww.enterprisejavanews.com>_
> * JSFCentral Interviews Podcast:
> http://www.jsfcentral.com/resources/jsfcentralpodcasts/
> * Sign up for the JSFCentral Newsletter:
> http://oi.vresp.com/?fid=ac048d0e17
>
> On Mon, Jan 12, 2015 at 12:00 PM, manfred riem
> <manfred.riem_at_oracle.com <mailto:manfred.riem_at_oracle.com>> wrote:
>
> Hi all,
>
> I like to close
> https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-49 as
> "Won't fix" as this request suffers from the chicken and the egg
> problem. In this particular case we cannot make sure the client id
> is rendered before the JavaScript executes.
>
> Thoughts?
> Manfred
>
>