ihelper-mts.ru -- XML Parsing Error: not well-formed on XHTML page; serves different (broken) content to non-"Firefox" browsers

RESOLVED WORKSFORME

Status

Tech Evangelism Graveyard
Other
RESOLVED WORKSFORME
9 years ago
3 years ago

People

(Reporter: kmike, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.9.1.3pre) Gecko/20090806 SeaMonkey/2.0b2pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.9.1.3pre) Gecko/20090806 SeaMonkey/2.0b2pre

Seamonkey croaks on the invalid XHTML page.


Reproducible: Always

Steps to Reproduce:
1. Load the page: https://ihelper.mts.ru/selfcare/

Actual Results:  
XML Parsing Error: not well-formed
Location: https://ihelper.mts.ru/selfcare/
Line Number 19, Column 27:
		if (tbPwd.value.length <= 0) {
----------------------------------------^


Expected Results:  
Page displays correctly.

I believe the embedded Javascript snippets should be enclosed in the CDATA tags in a XML document, hence the error. But Firefox 3.5 is much more forgiving, and it is able to render the page fine.

Comment 1

9 years ago
This is an error of the website, and it looks the same with current Firefox development builds ("Minefield").
Assignee: nobody → other
Component: General → Other
Product: SeaMonkey → Tech Evangelism
QA Contact: general → other

Comment 2

9 years ago
Happens in Camino, too. The fact that it's broken with Minefield and working with Firefox 3.5 sort of suggests a UA sniffing issue, and the fact that spoofing Camino as the Firefox 2.0 UA string *works* pretty much proves it.
Blocks: 334967
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Summary: XML Parsing Error: not well-formed on XHTML page → ihelper-mts.ru -- XML Parsing Error: not well-formed on XHTML page; serves different (broken) content to non-"Firefox" browsers
(Reporter)

Comment 3

9 years ago
Well, it's pretty weird, I can see zero differences in the page content if I save the page in FF35 and in Seamonkey 2.0b.
(Reporter)

Comment 4

9 years ago
Ok, so it appears the site is serving different content type to the different browsers:
for Firefox/3.5: Content-Type: text/html; charset=utf-8
for Seamonkey: Content-Type: application/xhtml+xml; charset=utf-8
(Reporter)

Comment 5

8 years ago
Everything's working now.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.