Show ID in the HTML pages

Vaadin 6 / 7 / 8 Framework UI
1

The HTML pages shown on the IE browser (or Firefox) generated by the GWT tool do not show the id of the HTML element.

How to modify the ITMILL components or GWT componenets (like Button, TextField, Table), so that the id of the component can be shown in the HTML element in the HTML page.

I have tried using the method setDebugId(“idString”) to set the id of the Button on the ITNMILL server side, this “isString” can be seen in the ITMILL client side of the Button (from UIDL), but will not shown in the HTML page.

2

May I ask, what you are trying to do with the ID?

Could this solve the problem? IT Mill Ltd is now Vaadin Ltd

3

Thank for your prompt replay, Joonas

I am using the open source test tool called “watij” Web Application Test in Java. Which allow me to write the web test program in Java, via the Internet Explorer, attach the web pages. From the web page, I am able to access the HtmlElement to retrieve data from components like TextField, ComboBox,Table and perform control on Button, Tab, etc…

I have already had the automated web page test software for our web product using the "watij’. Now we plan to enhance our web product with ITMILL tool kit, without the id in the cHtmlElement of the web pages generated by ITMIILL and GWT can be a big problem with our automated test.

Record and play back web page test method is not appropriate for our test requirement.

4

Hi!

Toolkit don’t put the debug id’s to html DOM by default. It does this currently only if toolkit is in “testing mode” using our separately sold Testing Tools product.

I can quickly come up with two methods how you can get forward:

  1. modify the client side engine a bit so that field called usePaintableIdsInDOM has “true” as its default value.

  2. fool the client side engine to be in Testing Tools mode by starting it with a custom html template. Check ApplicationServlet and ApplicationConnection classes for hints how you could do this.

The second option is rather big hack. In the first one you’ll end up having your own branch of toolkit with that. So no clean solution exists currently. I’ll keep in mind that it would be good to have an method to modify this behavior. If you have a patch for this, I’m happy to review and commit it.

cheers,
matti