348301 - linked css does not load in framed site when back button pressed.

Status: RESOLVED INCOMPLETE

(Core :: DOM: Core & HTML, defect)

Description

[larry]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.06) Gecko/20060728 Firefox/1.5.0.6

Framed site with nav frame and content frame. Content frame uses document.write to fill nav frame when it is loaded. Clicking link in content frame loads new page which uses document.write to re-fill nav frame. Nav frame includes linked stylesheet. When the back button is pressed, the stylesheet is not loaded and the following errors are generated:

Unexpected end of file while searching for ',' or '}'. Ruleset ignored due to bad selector.
Unexpected end of file while searching for closing } of invalid rule set.


Problem shows up in Firefox 1.5 WinXP and Win98. Firefox 1.0.8 is OK.


Reproducible: Always

Steps to Reproduce:
1. Use Firefox 1.5
 
2. See example: http://www.hawaiimeetings.com/ff_frameset.html

3. Press "Next Page" link.

4. Press "Back Button"


Actual Results:  
Top frame is white. Stylesheet not loaded.

Expected Results:  
Top frame is blue. Stylesheet loaded correctly

Forcing the browser to reload the stylesheet each time using a random extension to it (eg. ff_blue.css?f=b1234) did not fix the problem.

Comment 1

[Adam Guthrie]

An exact regression range for this might be helpful.

Comment 2

[Ria Klaassen (not reading all bugmail)]

Not possible to get an exact regression range. The last working build was 8 May 2004 but during the rest of the month it was obscured by crashes. At least until 26 May. 

Comment 3

[Martijn Wargers (dead)]

The crashes were probably caused by bug 244178.
I think this is a regression from bug 243034, the testcase uses document.write stuff.
With a 2004-05-08 build it works fine (like Ria said), with a 2004-05-10 build, it crashes.

Comment 4

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Hi Larry,

I have tried to test this issue using the provided steps from comment 0, but it seems that the provided page in no longer available. Can you please provide another one or maybe a test case, so we can try to reproduce this?

Also,  can you please retest this using latest Firefox release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E). 

Thanks,
Cosmin.

Comment 5

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Marking this as Resolved: Incomplete due to the lack of response from the reporter.
If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.