I have the following XML parsing issue. I load the following xml snippet from an xml file loaded from the backend and parse it with GWT (com.google.gwt.xml.client.*) that end up different in certain browsers/devices, see below. Present in xml file that is loaded: ------------------
<value><![CDATA[<div class="CookieMsg container"> <div class="Content"><p><strong>Leuker.nl</strong> is wettelijk verplicht toestemming te vragen voor het gebruik van cookies. Als je deze eenmalig accepteert, dan is de website Leuker.nl verder zonder onderbrekingen te bezoeken. Klik op 'accepteren' om verder te gaan. Meer informatie over ons cookiebeleid vind je <span data-type="popInfo" data-key="InfCkiMnuIt">hier</span>. <span class="Button">Accepteren</span></p></div></div>]]></value> ----------------- However, the app does throw an exception during parsing, with some browsers/devices, and analyzing the exception, the application indicates it's trying the load wrong/unexpected xml, namely: --------------- <value><![CDATA[<div class="CookieMsg container"> <div class="Content"> <p><strong>Leuker.nl</strong> is wettelijk verplicht toestemming te vragen voor het gebruik van cookies. Als je deze eenmalig accepteert, dan is de website Leuker.nl verder zonder onderbrekingen te bezoeken. Klik op 'accepteren' om verder te gaan. Meer informatie over ons cookiebeleid vind je <span data*]]><![CDATA[*-type="popInfo" data-key="InfCkiMnuIt">hier</span>. <span class="Button">Accepteren</span></p> </div> </div>]]></value> -------------- The error is because of a sudden closing and opening of the CDATA part (red in the above snippet). Any idea how this can happen? Analyzing the XML parsing, I can't determine a possible problem. It's like the browser 1) Is performing some auto-correct and thinks some error is determined and it tries to fix it. I't for sure not the piece of xml that is present in the loaded xml file as present above. 2) Or it can't handle attributes of the syntax "data-*" and will close and start a new tag when encountering "data-"... But it concerns modern browsers that should support this (see below) This happens at least with: 1) Latest Microsoft surface (touche device) with the Chrome browser in Windows 10, with user agent (a co-worker is experiencing this): ----- [mozilla/5.0 (windows nt 10.0; wow64; trident/7.0; .net4.0c; .net4.0e; .net clr 2.0.50727; .net clr 3.0.30729; .net clr 3.5.30729; infopath.3; rv:11.0) like gecko] ----- 2) The following user agent (encountered in an occurred exception, about the same as above): mozilla/5.0 (windows nt 6.1; wow64; trident/7.0; slcc2; .net clr 2.0.50727; .net clr 3.5.30729; .net clr 3.0.30729; media center pc 6.0; .net4.0c; .net4.0e; infopath.3; rv:11.0) like gecko] Note: it runs well on a Windows 10 desktop/laptop without touch functionality. Any idea? Please let me know how to solve/analyze this, as I found it hard to solve it and I am stuck. - Ed -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
