| Summary: | Enable rendering of HTML element IDs for RAP widgets | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Nick Mussin <nmussin> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | tbuschto | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M5 | ||||||
| Hardware: | All | ||||||
| OS: | other | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Nick Mussin
Created attachment 208627 [details]
introduces support for optional rendering of html ids for widgets. plus small refractoring of ProtocolTest.js
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. @Tim: Should we rather use qxsettings or qxvariants instead of the field qx.ui.core.Widget._renderHtmlIds to decide if ids should be written? 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. 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. |