32794+bytes xml error "Input is not proper UTF-8"
Reported by
guitarpo...@gmail.com,
Jun 1 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.63 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Save the attached XML. 2. Open saved XML. Displays: ``` This page contains the following errors: error on line 771 at column 16: Input is not proper UTF-8, indicate encoding ! Bytes: 0xE2 0x82 0xAC 0x0A Below is a rendering of the page up to the first error. ... ``` What is the expected behavior? This error should not happen. What went wrong? Displays: ``` This page contains the following errors: error on line 771 at column 16: Input is not proper UTF-8, indicate encoding ! Bytes: 0xE2 0x82 0xAC 0x0A Below is a rendering of the page up to the first error. ... ``` However, if you were to reduce the one character , then , this error does not occur . 3. Edit the XML like: ```diff <?xml version="1.0" encoding="UTF-8"?> <source> -<xyz><abcd>12345678901234567</abcd></xyz> +<xyz><abcd>1234567890123456</abcd></xyz> <xyz><abcd>12345678901234567</abcd></xyz> ``` 4. Open the XML again. Now no error occurs. :( ...??? Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 51.0.2704.63 Channel: stable OS Version: OS X 10.10.1 Flash Version: Shockwave Flash 21.0 r0
,
Jun 9 2016
Faced the same issue in our XML exports. Firefox and linter report OK, chromium/chrome says "Input is not proper UTF-8". Chromium 50.0.2661.102 Ubuntu 14.04 (64-bit) Chrome 51.0.2704.79 on Windows
,
Jun 10 2016
,
Jun 13 2016
Tested the issue on Windows 7, Mac 10.11.5, Ubuntu 14.04 using 51.0.2704.63, latest stable 51.0.2704.84, canary 53.0.2766.0 as per above steps and observed below observations: 1.Page displayed with error in chrome stable 51.0.2704.63, latest stable 51.0.2704.84 versions. 2.Page displayed without errors in chrome latest dev 53.0.2763.0, canary 53.0.2766.0, beta 52.0.2743.33, firefox. Please find attached screenshots of stable,canary and firefox. guitarpopnot330@Could you please confirm the expected behavior for further triaging the issue.
,
Jun 14 2016
I saw 616423.jpg. It looks good to me! > canary and firefox
,
Jun 14 2016
====================================== 51.0.2662.0 Base Position: 378134 Bad Build: 51.0.2675.0 Base Position: 380818 ====================================== Able to repro this issue on Windows 7, MAC (10.11.5) & Ubuntu Trusty (14.04) for the Google Chrome Stable Version - 51.0.2704.84 This is a regression issue broken in M51, below mentioned is the bisect info: CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/9adffced4162398edd53ba0c64074e0916ddf43d..0b5cac87b6b7f1ad537779787240464b0f580a9c Suspecting Commit: 0b5cac87b6b7f1ad537779787240464b0f580a9c Review URL: https://codereview.chromium.org/1752223002 @dominicc: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner. Thank you.
,
Jun 14 2016
,
Jun 14 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 16 2016
From comment 4 it looks like this has been fixed by libxml 2.9.4. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by shrike@chromium.org
, Jun 3 2016Status: Untriaged (was: Unconfirmed)