Issue Details (XML | Word | Printable)

Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Ed Burns
Votes: 9
Watchers: 1

If you were logged in you would be able to see more operations.

JS function for "give me the clientId"

Created: 04/Oct/04 10:56 AM   Updated: 08/Nov/13 09:15 PM
Component/s: Ajax/JavaScript
Affects Version/s: 2.0
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File changebundle.txt (9 kB) 06/Nov/08 06:44 PM - Ed Burns


Operating System: All
Platform: Sun

Issuezilla Id: 49
Status Whiteboard:

EGTop5 effort_hard cat2 jsdoc size_medium importance_small draft

Participants: Ed Burns and rogerk

 Description  « Hide

EB> R1 something you can stick in your page, that will evaluate to the full,
EB> absolute, clientId of the named thing when the page is rendered. Like
EB> this:

AVK> <h:button id="button1"
AVK> onclick="button_setEnabled(button2,
AVK> false);button_clicked(button1);return"
AVK> ... />
AVK> <h:button id="button2" ... " />

AVK> then I want the result of the first one to be

AVK> <input type="submit" id="myform:button1"
AVK> onclick="button_setEnabled('myform:button2', false);
AVK> button_clicked('myform:button1'); return;"
AVK> ... />

EB> R2 This thing can be presenent in an attribute value, or as template
EB> text.

AVK> Definitely needed in an attribute value, for the method invocation. I
AVK> don't know whether it is necessary in tempate text. I have a feeling
AVK> some JavaScript interpreters barf if you mention the id before the
AVK> element is present.

EB> R3 This thing must only work within the scope of a naming
EB> container. In other words, I can't use this mechanism to refer
EB> to something in form B if I'm inside Form A.

EB> R4 This thing must work in a multi-include page scenario

EB> R5 This thing must work in a portlet scenario

Ed Burns added a comment - 23/Feb/05 10:22 AM

push to 2.0

Ed Burns added a comment - 09/Sep/08 01:28 PM


Ed Burns added a comment - 12/Sep/08 05:19 PM


Ed Burns added a comment - 21/Oct/08 07:48 AM
      • Issue 293 has been marked as a duplicate of this issue. ***

Ed Burns added a comment - 21/Oct/08 01:04 PM

Change summary

Ed Burns added a comment - 06/Nov/08 01:53 PM

Given the #{component} and #{compositeComponent} implicit objects, and the ability to use them on the
server side, in XHTML, and in resources, having the ability to say #{component.clientId} would be nice. To
do this, we need to add to UIComponent, String getClientId(). This just does
FacesContext.getCurrentInstance() and calls the other getClientId().

Ed Burns added a comment - 06/Nov/08 06:44 PM

Created an attachment (id=163)
Fix for this bug, first iteration.

Ed Burns added a comment - 28/Jul/09 12:08 PM

Push out to 2.1

Ed Burns added a comment - 24/Nov/09 07:48 AM

Prepare to delete "spec" subcomponent.

Ed Burns added a comment - 14/Dec/09 08:59 AM

Move these to unscheduled because we need to target them correctly. isn't
specific enough.

rogerk added a comment - 05/Mar/10 06:57 AM


Ed Burns added a comment - 17/Mar/10 01:51 PM


Ed Burns added a comment - 27/Apr/10 10:55 AM

no sig change

Ed Burns added a comment - 15/May/10 07:54 AM

These are targeted at 2.1.

Ed Burns added a comment - 08/Jun/10 12:58 PM


rogerk added a comment - 27/Oct/10 10:50 AM


Ed Burns added a comment - 04/Feb/12 02:41 AM

Remove from consideration for 2.2