This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21384 - If this is meant to serve as a tool to make custom alert, confirm and prompts and at the same time server as a replacement for showModalDialog, then there should be an option to halt javascript execut [...]
Summary: If this is meant to serve as a tool to make custom alert, confirm and prompts...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-25 09:15 UTC by contributor
Modified: 2013-04-14 06:45 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-03-25 09:15:06 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html
Multipage: http://www.whatwg.org/C#the-dialog-element
Complete: http://www.whatwg.org/c#the-dialog-element

Comment:
If this is meant to serve as a tool to make custom alert, confirm and prompts
and at the same time server as a replacement for showModalDialog, then there
should be an option to halt javascript execution when showModal is called.

Posted from: 84.234.179.60
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.40 Safari/537.31
Comment 1 Ian 'Hixie' Hickson 2013-04-01 17:58:56 UTC 
Well JS execution still needs to run, since the dialog itself might be interactive.

It's more meant to serve as a replacement for <div> used for dialogs, as is common on sites today.
Comment 2 Ian 'Hixie' Hickson 2013-04-14 06:45:16 UTC 
I don't really know how to provide the feature requested here. If anyone has any suggestions, please reopen this bug. Thanks!