New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 712500 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ dominicc@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Empty XML document not consistently reported as an error

Reported by bzbar...@mit.edu, Apr 18 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0

Steps to reproduce the problem:
1. Load attach testcase.

What is the expected behavior?
There's an error message in the iframe that looks similar to the error message below the iframe.

What went wrong?
There is no error message in the iframe.

Did this work before? No 

Does this work in other browsers? No
 Safari has the same bug.  Firefox does not.

Chrome version: 59.0.3067.0 (Official Build) dev (64-bit)  Channel: n/a
OS Version: OS X 10.12
Flash Version: 

The HTML spec does allow not reporting errors for XML documents in iframes.  But for other XML errors Blink reports them... it's just this one that doesn't get reported.
baz.html
266 bytes View Download

Comment 1 by jmukthavaram@chromium.org, Apr 18 2017

Labels: M-60 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Thanks for filing the issue.

Able to reproduce the issue on Mac-10.12.2,Windows 7 & Ubuntu 14.04  using Chrome stable version-57.0.2987.133 and Canary-60.0.3073.0 with the steps mentioned in comment#0.Observed no error message in the iframe after loading above html file.

This is Non-regression issue, Observed from M30 builds and confirming this issue to get more inputs from Dev team.

Please find the attached screen cast for reference.
712500.mp4
286 KB View Download

Comment 2 by nasko@chromium.org, Apr 19 2017

Owner: dominicc@chromium.org
Adding dominicc@ for opportunistic first line triage.

Comment 3 by dominicc@chromium.org, Apr 24 2017

Labels: -Pri-2 OS-Android OS-Chrome Pri-3
Status: Assigned (was: Untriaged)
It looks like there's no error reported because we don't treat data:application/xml, as an error but an empty document.

Comment 4 by bzbar...@mit.edu, Apr 24 2017 

Except in DOMParser you treat it as an error...

Comment 5 by dominicc@chromium.org, Apr 27 2017 

Yeah. This is inconsistent and probably wrong. I'm just reporting a bit of debugging: The problem isn't that there's an error that's not reported; it's that there's no error in the first place.

I haven't debugged where the zero-length content from the data: URL is going off the rails. FWIW if you serve Chromium 0 bytes of application/xml content we also treat that as an empty XML document whereas FF displays its XML error UI.

Comment 6 by dominicc@chromium.org, Aug 22 2017

Cc: dominicc@chromium.org
Owner: ----
Status: Available (was: Assigned)
Bulk disowning per sshruthi's email about bug triage best practices.
Project Member

Comment 7 by sheriffbot@chromium.org, Aug 22

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment