Hello Everyone,
I have read that inorder to facilitate integration with automated testing
tools
such as selenium which rely on DOM element "id", it is a good practice to
use ensureDebugId,
as this can be compiled out for production release, and result in zero
overhead.
However I need to use element id for an entirely different purpose.
1- Integrate my GWT widgets with third-party JavaScript plugins.
for example, plugin X requires my elements have a particular id,
inorder for the plugin to work,eg. applying effects on elements with id
X
2- When I need to do low level DOM manipulation,
I believe if I set an ID for an element it would be easier to retrieve
it
through getElementById.
- do you think I need to use DOM.setElementAttribute instead of
ensureDebugId ?
- should I avoid using element ID alltogether and find another solution ?
(assumption being relying on element ID is considered a hack, and not an
elegant solution, is this correct ?)
- will this ID remain fixed during multiple compile ?
Thank You
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
