Closed
Bug 303255
Opened 19 years ago
Closed 19 years ago
<marquee> tags stop scrolling when going back with bfcache enabled
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: dave_harper, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
458 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050802 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050802 Firefox/1.0+ When hitting back on a page with a scrolling marquee, the marquee stops scrolling in the position that it was in when you left the page. Reproducible: Always Steps to Reproduce: 1. Goto a page with a scrolling marquee. 2. Navigate to a different link 3. Hit back Actual Results: Marquee on original page has frozen in position Expected Results: Marquee should be scrolling as specified
Reporter | ||
Comment 1•19 years ago
|
||
Attached a testcase.
Reporter | ||
Updated•19 years ago
|
Component: History → History: Session
Product: Firefox → Core
Version: unspecified → Trunk
Updated•19 years ago
|
Blocks: blazinglyfastback
Comment 2•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050803 Firefox/1.0+ ID:2005080303 I see this too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•19 years ago
|
||
Regression between ID:2005073013 and ID:2005073111.
Updated•19 years ago
|
Keywords: regression
Reporter | ||
Comment 5•19 years ago
|
||
303267 Fixed This. Although it is a little juddery when coming back, I don't think it warrents a new bug.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 6•19 years ago
|
||
Verified FIXED for me using the testcase at https://bugzilla.mozilla.org/attachment.cgi?id=191487 under build 2005-08-16-12 on Windows XP SeaMonkey trunk.
Status: RESOLVED → VERIFIED
Component: History: Session → Document Navigation
QA Contact: history → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•