Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366929 - Enable rendering of HTML element IDs for RAP widgets
Summary: Enable rendering of HTML element IDs for RAP widgets
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All other
: P3 enhancement (vote)
Target Milestone: 1.5 M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-16 06:18 EST by Nick Mussin CLA
Modified: 2011-12-22 12:46 EST (History)
1 user (show)

See Also:

Attachments
introduces support for optional rendering of html ids for widgets. plus small refractoring of ProtocolTest.js (6.04 KB, patch)
2011-12-20 10:31 EST, Nick Mussin CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Mussin CLA 2011-12-16 06:18:56 EST 
RAP currently does not write id attributes into the HTML document. The ARIA accessibility framework, for example, heavily relies on element IDs to express relationships between different widget roles.

Enabling RAP to write widget IDs directly in the HTML document will help to support ARIA.

There should be a way to enable or disable the rendering of element IDs manually. By default, this feature should be disabled.
Comment 1 Nick Mussin CLA 2011-12-20 10:31:17 EST 
Created attachment 208627 [details]
introduces support for optional rendering of html ids for widgets. plus small refractoring of ProtocolTest.js
Comment 2 Ralf Sternberg CLA 2011-12-21 05:38:48 EST 
With this patch, setting the field qx.ui.core.Widget._renderHtmlIds to true results in all widgets ids to be written as id attributes to the DOM. We may think about a better client API...
Applied patch to CVS HEAD.
Comment 3 Ralf Sternberg CLA 2011-12-22 05:28:54 EST 
@Tim: Should we rather use qxsettings or qxvariants instead of the field qx.ui.core.Widget._renderHtmlIds to decide if ids should be written?
Comment 4 Tim Buschtoens CLA 2011-12-22 05:39:56 EST 
A variant would be good if it would be set before the Widget.js is parsed, but since i cant see that happening, its ok the way it is.
Comment 5 Ralf Sternberg CLA 2011-12-22 12:46:58 EST 
Ok, then let's keep it as it is for now.
This client-side mechanism is now also used when WidgetUtil.ENABLE_UI_TESTS is set as a system property. Currently it's rendered as an additional Display property "enableUiTests". Not quite happy with this though.