Closed
Bug 619646
Opened 14 years ago
Closed 14 years ago
Page refresh doesn't work iff javascript confirm prompt closed with ESC (and script contains document.write)
Categories
(Core :: General, defect)
Core
General
Tracking
()
RESOLVED
DUPLICATE
of bug 619644
People
(Reporter: kdevel, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
text/html
|
Details |
User-Agent: Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b9pre) Gecko/20100101 Firefox/4.0b9pre After pressing ESC on confirm dialog page cannot be reloaded. Reproducible: Always Steps to Reproduce: 1. open testcase https://bug616109.bugzilla.mozilla.org/attachment.cgi?id=494685 2. press ESC twice 3. press Ctrl-Shift-R or click shift reload Actual Results: "v = false" Expected Results: Page is reoaded and rerendered including a new confirm dialog. Built from http://hg.mozilla.org/mozilla-central/rev/8755d308796d
Comment 1•14 years ago
|
||
Confirmed using Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20101216 Firefox/4.0b9pre ID:20101216030331 Does not occur in 3.6.13. Last good nightly: 2010-11-19 First bad nightly: 2010-11-20 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6478c1b83d60&tochange=baa6cc2f72e4 Suspect: Bug 59314 - Alerts should be content-modal, not window-modal Given that this regression range matches bug 619644, believe this may be fixed when that is fixed. Marking that bug as a dependency. See also: Bug 619645
Comment 2•14 years ago
|
||
(Can someone put this in the correct product/component please. The suspected cause is Toolkit:General, but not sure if this belongs there also).
Blocks: 59314
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Depends on: 619644
Ever confirmed: true
Keywords: regression
OS: Linux → All
Product: Firefox → Core
QA Contact: general → general
Hardware: x86_64 → All
Summary: confirm dialog: strange ESC-behavior (3) → Page refresh doesn't work iff javascript confirm prompt closed with ESC (and script contains document.write)
Version: unspecified → Trunk
This is the same underlying issue as Bug 619644. We end up in some bizarre place where we've aborted the document load but are still running script on it which causes the bogus sessionhistory entry.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
No longer depends on: 619644
Updated•14 years ago
|
blocking2.0: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•