Closed
Bug 312816
Opened 19 years ago
Closed 19 years ago
onload doesn't fire on page with warning at history.back()
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: cmess1na, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(2 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
If a page with an onload have a warning and then I do an history.back(), the
onload event doesn't fire.
Reproducible: Always
Steps to Reproduce:
1. Load pippo3.html
2. Click on 'seleziona'
3. Click on 'back'
Expected Results:
fire event onload
Comment 3•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051018
Firefox/1.6a1 ID:2005101804
Confirming. This doesn't occur when bfcache is off.
Blocks: blazinglyfastback
Summary: Onload doesn't fire on page with warning at history.back() → onload doesn't fire on page with warning at history.back()
Version: unspecified → Trunk
Comment 4•19 years ago
|
||
Attachment #199911 -
Attachment is obsolete: true
Comment 5•19 years ago
|
||
Click the link, then click the link to go back. An alert should popup when
onload is fired.
Comment 6•19 years ago
|
||
I believe this is intentional. When pages are loaded from the bfcache, the
onload handler doesn't fire. You can use the new pageshow event if you want
something to happen every time the page is displayed.
See http://developer.mozilla.org/en/docs/Using_Firefox_1.5_caching
Changing resolution to RESOLVED INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•19 years ago
|
||
*** Bug 316850 has been marked as a duplicate of this bug. ***
Comment 8•19 years ago
|
||
*** Bug 316948 has been marked as a duplicate of this bug. ***
Component: History → Bookmarks & History
QA Contact: history → bookmarks
You need to log in
before you can comment on or make changes to this bug.
Description
•