Closed
Bug 851968
Opened 13 years ago
Closed 13 years ago
Site doesn't work in FF19.0.2, all other versions OK
Categories
(Firefox :: Untriaged, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: rvjanc, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130313170052
Steps to reproduce:
Went to
http://www.graham-mitchell.com/ using FF19.0.2 and the images will not load.
FF17 - Works
FF18 - Works
FF20b5 - Works
FF21a2 - Works
Actual results:
As noted the site loads images for versions of FF17/18/20b/21a but not FF19.
It also works in Chrome and Safari [latest versions].
Expected results:
See above.
Comment 1•13 years ago
|
||
I'm glad it works in Firefox 20. That means it will be fixed in a couple of weeks when that version comes out.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
I did get this from the error console when using FF19.
Error: not well-formed
Source File: http://www.graham-mitchell.com/data/xml/header.xml
I didn't get that error with FF18 or FF20b.
So the web site's owner simply needs to have his viewers wait until April; great solution!
Also see this:
http://forums.mozillazine.org/viewtopic.php?f=38&t=2679803&p=12739037#p12739037
which points to the issue.
Comment 3•13 years ago
|
||
Nobody reported it during the Aurora or Beta phases of 19, nor was it reported for the first 4 weeks that Firefox 19 was out. Waiting another 2 weeks seems would not seem to be a problem, therefore.
It seems that the XML files which work have the following header:
<?xml version="1.0" encoding="UTF-8"?>
and the ones which don't work have the following header:
<?xml version="1.0" encoding="UTF-16"?>
I assume this is a bug with FF19? UTF-16 should be supported.
Comment 5•13 years ago
|
||
Probably bug 844007
Comment 6•13 years ago
|
||
Fixed it, I mean.
Comment 7•13 years ago
|
||
In case that it's bug 844007 it would be still a bug in the page.
(utf-16 encoding declared for utf-8 content)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•