1491125 - No kitty cat sightings :-(

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P3)

Description

[Justin Dolske [:Dolske]]

Attachment: Expected map contents in Safari

The "Puma Sightings Map" on http://www.bapp.org/puma-sighting-map does not load any sightings, i.e. various colored map markers. Works fine in Chrome (well, at least Canary) and Safari.

There are a few warnings in the console, the first two ("no longer supported") are also shown in Safari, but not the XML errors.


unreachable code after return statement[Learn More] 
js_3d8cbd7dff1b1d9e25d72c359bb4fc37.js:19:13091

Control is no longer supported in the Google Maps Javascript API v2. Please visit https://developers.google.com/maps/documentation/javascript/v2/v2tov3 to migrate your application to v3. maps:188:35

Map.addControl is no longer supported in the Google Maps Javascript API v2. Please visit https://developers.google.com/maps/documentation/javascript/v2/v2tov3 to migrate your application to v3. maps:188:35

XML Parsing Error: not well-formed
Location: http://www.bapp.org/genxml.php?cachebuster=1536865239786
Line Number 2, Column 538721: genxml.php:2:538721

XML Parsing Error: not well-formed
Location: http://www.bapp.org/puma-sighting-map
Line Number 2, Column 538721: puma-sighting-map:2:538721

Comment 1

[Justin Dolske [:Dolske]]

Forgot to note -- tested in current release, with a new profile. There is a map shown, just no markers.

Comment 2

[Mike Taylor [:miketaylr]]

(In reply to Justin Dolske [:Dolske] from comment #0)
> XML Parsing Error: not well-formed
> Location: http://www.bapp.org/genxml.php?cachebuster=1536865239786
> Line Number 2, Column 538721: genxml.php:2:538721
> 
> XML Parsing Error: not well-formed
> Location: http://www.bapp.org/puma-sighting-map
> Line Number 2, Column 538721: puma-sighting-map:2:538721

I ran the XHR response from genxml through an XML validator and got the following, 

2: 538721	An invalid XML character (Unicode: 0xb) was found in the value of attribute "description" and element is "sighting".

Tom, you know more about XHR/unicode than I do. Any ideas? Or is this a red herring...

Comment 3

[Thomas Wisniewski [:twisniewski]]

This is just plain old site error. Their genxml.php is in fact generating invalid XML, with vertical tab characters in the text, the first of which is right where the column number of the console logged message mentions (appears as a ^K here):

>A deer carcass had been noted at photo site. ^KImage credit: Bill Korbholz and Kathy Korbholz through Friend

There are 6 or 7 such vertical tabs, and once I remove those the file seems otherwise valid.

They're basically just fetching this via XHR, reading the responseText, then feeding it into Google Map's GXml.parse(data) API, which does this:

>(new DOMParser).parseFromString(xhr.responseText,"text/xml")

The interop issue stems from Chrome's DOMParser not caring that the XML is invalid, and just parsing it regardless. Similarly, their XHR code parses it as well when using responseType=document. Firefox and Edge treat both attempts as errors. Unsurprisingly Safari agrees with Chrome.

To my eye this would seem to be Blink and WebKit's interop bug, given that invalid XML is not meant to be parseable (and indeed both browsers complain quite loudly when you try to load the same document in their URL bars).

But either way, the site should fix their XML or use another format that isn't as strict with control characters.

Comment 4

[Ksenia Berezina [:ksenia] on leave until 09/15]

Attachment: Screen Shot 2021-01-12 at 3.48.08 PM.png

The issue with markers appears to be fixed

Comment 5

[Oana Arbuzov [:oanaarbuzov]]

I can't reproduce the issue either.
https://prnt.sc/x7z1or

Tested with:
Browser / Version: Firefox Nightly 86.0a1 (2021-01-18)
Operating System: Windows 10 Pro