[FIX]Unable to load page http://www.one.lt

RESOLVED FIXED

Status

()

Core
DOM
P5
normal
RESOLVED FIXED
10 years ago
5 years ago

People

(Reporter: Tomas, Assigned: bz)

Tracking

({regression})

Trunk
regression
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.9 +
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007092223 Minefield/3.0a9pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007092223 Minefield/3.0a9pre

Page http://www.one.lt doesn't load with any build of FF3. Well, indeed it does: I can see main page for a few second, but then it redirects my to page, saying, that page can't be loaded. There is no problem using FF2 or any other browser.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.one.lt
Actual Results:  
Image http://c19.one.lt/res/images/labels/tmp_close2_lt.gif is showed up in spite of main page.

Expected Results:  
To see main page of http://www.one.lt and be able to browse it.
(Reporter)

Updated

10 years ago
Summary: Redirects to page, saying that main page can't be loaded → Unable to load page http://www.one.lt
(Reporter)

Comment 1

10 years ago
Just noticed, that same thing happens with page http://www.videogaga.lt. Both of these pages are build be same developers and, indeed, I think, that it's done pretty bad. So, the problem is bad code of these pages, but on the other side, both of them work OK with FF2 and all other browsers.
OS: Windows XP → All
Hardware: PC → All
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007092216 Minefield/3.0a9pre ID:2007092216

Confirmed, works in IE7 and Opera 9.22

Martijn, can you figure out what's going on here ?
I see a truckload of warnings in the console but none seem to be a reason for the page not properly loading.
(Reporter)

Comment 3

10 years ago
My guess is that problem is connected to CSS of these pages. Firebug shows this errors while loading http://videogaga.lt (while loading http://one.lt I see many more similar errors):

Expected declaration but found '/'. Skipped to next declaration.
[Break on this error] undefined
main.css (line 493)
Error in parsing value for property 'filter'. Declaration dropped.
[Break on this error] undefined
main.css (line 494)
Expected declaration but found '/'. Skipped to next declaration.
[Break on this error] undefined
main.css (line 501)
Error in parsing value for property 'filter'. Declaration dropped.
[Break on this error] undefined
main.css (line 502)
Selector expected. Ruleset ignored due to bad selector.
[Break on this error] undefined
main.css (line 905)
User Agent sniffing?
(Reporter)

Comment 5

10 years ago
Don't think so. Firstly, I don't see point of developers of these sites to block FF3. Especially, not Firefox in general, but just Firefox 3. Secondly, I've tried "User agent switch" (or something like that) extension, to change user agent. It didn't change a thing about loading these sites.
I get a regression range between 2007-07-08 and 2007-07-09:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-07-08+04&maxdate=2007-07-09+07&cvsroot=%2Fcvsroot
I guess a regression from bug 373231, bug 382947 or bug 372969.
Component: General → General
Product: Firefox → Core
QA Contact: general → general
I'll narrow it down later today
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
regressionwindow
works in 20070708_1921_firefox-3.0a7pre.en-US.win32
fails in 20070708_1936_firefox-3.0a7pre.en-US.win32

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&filetype=match&whotype=match&sortby=Date&hours=2&date=explicit&mindate=1183947660&maxdate=1183948559&cvsroot=%2Fcvsroot

-> Bug 382947
Blocks: 382947

Updated

10 years ago
Flags: blocking1.9?
Version: unspecified → Trunk
As a sidenote, see this page of why it's so difficult to get a testcase out of the page:
http://my.opera.com/hallvors/blog/2007/03/27/how-to-say-hello-world-with-javascript
Has anyone contacted the site yet?
Blocks: 398280
OK.  Let's get to the bottom of this.  +'ing.  Works fine in Fx 2 and Safari.  Moving to DOM.
Component: General → DOM
Flags: blocking1.9? → blocking1.9+
Priority: -- → P5
QA Contact: general → general
(Reporter)

Comment 12

10 years ago
So it's going to be fixed?
Tomas the problem is going to be investigated. That is no guarantee it will be fixed, but one would hope so.
OK, so the issue here is that we used to send:

  Content-Type: text/plain; charset=utf-8

Now we send:

  Content-Type: text/plain; charset=UTF-8

and this seems to make the site blow up.  Looks a lot like bug 398280 indeed.
I think the right fix here is to leave the existing charset if it matches the one we want to set (up to case).  I'll probably roll that change into the fix for bug 393968.
Depends on: 393968
Assignee: nobody → bzbarsky
Summary: Unable to load page http://www.one.lt → [FIX]Unable to load page http://www.one.lt
Fixed by checkin for bug 393968.  Checked in a test too.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Flags: in-testsuite+
Resolution: --- → FIXED

Comment 17

6 years ago
See tests in <http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0955.html>. It appears that, as of 2011, only FF tries to preserve the charset casing (where Opera and IE preserve it because they do not fix the charset at all).
Yes, but the upshot is that for pages that set the charset the three have compat.

If course you can try backing this patch out and seeing whether this site breaks, as well as the site in bug 398280.

Comment 19

5 years ago
See related XHR issue: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16302

Comment 20

5 years ago
(In reply to Julian Reschke from comment #19)
> See related XHR issue: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16302

Sorry, wrong link.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16303
You need to log in before you can comment on or make changes to this bug.