I’ve noticed we get … in the parsed HTML in the browser that don’t exist
in the source HTML. It appears to be a side-effect of the browser
parsing the HTML and adding “missing” tags. I would expect different
engines to end up with different results at times.
-Mike
On 4/16/25 11:46, Thomas Broyer wrote:
That doesn't look like DOM created by GWT widgets themselves, more
like some third-party library. If that's the case, then updating GWT
shouldn't change anything.
On Wednesday, April 16, 2025 at 4:42:28 PM UTC+2 [email protected]
wrote:
hI, I am using 2.10.0 GWT version but But I noticed that the page
is built differently between Chrome and Firefox. In particular, I
find myself a <tbody> more on Firefox. Do you think that updating
the version of GWT can help me? Thank you.
--
You received this message because you are subscribed to the Google
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/google-web-toolkit/c14c4a28-ab3f-468e-9e59-93fa158194dcn%40googlegroups.com
<https://groups.google.com/d/msgid/google-web-toolkit/c14c4a28-ab3f-468e-9e59-93fa158194dcn%40googlegroups.com?utm_medium=email&utm_source=footer>.
​
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/google-web-toolkit/ad2ae275-9630-4cb6-9e59-38c0d00dacad%40newsrx.com.
