Closed
Bug 619443
Opened 14 years ago
Closed 14 years ago
Inconsistent showing of "Prevent this page from creating additional dialogs" option
Categories
(Toolkit :: General, defect)
Toolkit
General
Tracking
()
RESOLVED
DUPLICATE
of bug 614151
People
(Reporter: jk1700, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20101215 Firefox/4.0b9pre
Build Identifier:
When executing the script from firebug console:
- setTimeout(print, 100); setTimeout(print, 100); - the "Prevent..." option doesn't appear
- setTimeout("print()", 100); setTimeout("print()", 100); - option appears
Reproducible: Always
Blocks: alertloops
Version: unspecified → Trunk
Comment 1•14 years ago
|
||
I guess print function is something like: alert("foo"); ?
I tried with |function print() { alert("foo"); }| and it worked well. Could you double-check?
Component: DOM: Core & HTML → General
OS: Windows 7 → All
Product: Core → Toolkit
QA Contact: general → general
Hardware: x86 → All
No, print function is something like window.print, just copy/paste both snippets to firebug console. I've checked it once again and it works as I explained - in the first example there is print dialog (press cancel) and print dialog, in the second example there is print dialog, prevent dialog, print dialog.
It works also if you replace print with alert ("print()" with "alert(0)") - in the first example you will have alert box + alert box, and in the second one you will have alert box + alert box with prevent checkbox
Comment 3•14 years ago
|
||
Indeed, this doesn't show the checkbox to prevent showing popups:
data:text/html,<script>setTimeout(alert, 100); setTimeout(alert, 100);</script>
But this does:
data:text/html,<script>setTimeout("alert(0)", 100); setTimeout("alert(0)", 100);</script>
(For some reasons, print() doesn't work for me...)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•14 years ago
|
||
This is actually a dupe of bug 614151.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•