Closed Bug 4279 Opened 21 years ago Closed 20 years ago

[FEATURE] JavaScript Alert dialogs

Categories

(Core :: DOM: Core & HTML, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: gerardok, Assigned: davidm)

References

Details

(Whiteboard: is this fixed now?)

Version: Seamonkey
Program: Viewer.exe
BuildID: mar_180610
Platform: WinNT

The JavaScript alert command is not opening any dialog box.

I've noticed it sends output to console. This failure possibly happens on other
platforms.

Steps to reproduce:

1. Create an HTML file with the following content:

<html>
<head>
<title>MyPage</title>
</head>
<body>
<script>
alert("Alert dialog opened");
</script>
</body>
</html>

2. Load that file in the browser

Actual Results: No dialog box is opened.
Expected Results: A dialog containing the "Alert dialog opened" string.
QA Contact: 4616 → 4015
Status: NEW → ASSIGNED
Summary: JavaScript Alert dialogs not displayed
Hardware: PC → All
The same is happening on Linux and Mac, with the caviat that there is no
console to sent the output to on Mac. Platform changed to All.
Target Milestone: M6
Target Milestone: M6 → M7
*** Bug 6974 has been marked as a duplicate of this bug. ***
Severity: normal → major
OS: Windows NT → All
The described failure applies to Apprunner also. Apprunner doesn't display any
output to the console. Severity changed to Major.
Assignee: vidur → don
Status: ASSIGNED → NEW
Target Milestone: M7
I just commited changes so that prompt() and confirm() are also defined (alert()
has been for a while). All of these calls get sent up to the implementor of
nsINetSupport. This is currently in browser land. The plumbing on the JS side
exists. It's up to one of Don's people to hook up the UI.
Assignee: don → davidm
Priority: P3 → P1
Summary: JavaScript Alert dialogs not displayed → [FEATURE] JavaScript Alert dialogs
Target Milestone: M8
David, what are we dependant upon before this can be completed?
Status: NEW → ASSIGNED
The problem is that if I make the webshell window impliment the NetSuport
interface ( which I did in the past ), the dialogs don't load. I don't know why
but until necko lands I really don't want to look into it.
Target Milestone: M8 → M9
Move to m9 since Necko didn't land
*** Bug 9346 has been marked as a duplicate of this bug. ***
Blocks: 8310
This is a stopper for people writing JavaScript and using alert() for debugging.
I suspect they can use dump() in the interim, but it would be great to at least
have alert() write out to the console as it does in Viewer.
Blocks: 10575
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
I checked in the code to hook up the UI. There are still problems in that you are
unable to bring up the dialog from certain points in the code but I believe I
have bugs on most of them
Status: RESOLVED → REOPENED
Status: REOPENED → NEW
Re-tested on 07/28 build. A dialog box opens now but the alert msg is not being
displayed. A dialog box containing the "Alert dialog opened" string is expected.
Bug reopened.
Resolution: FIXED → ---
Re-tested on 07/28 build. A dialog box opens now but the alert msg is not being
displayed. A dialog box containing the "Alert dialog opened" string is expected.
Bug reopened.
*** Bug 5127 has been marked as a duplicate of this bug. ***
Depends on: 11611
The dialogs should come up. However they will not be modal until after danm
fixes 11611 so Confirm and Prompt will not return correct values.
Whiteboard: is this fixed now?
Status: NEW → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
fix checked in.
Status: RESOLVED → VERIFIED
Verified fix on 8/20 build on Win NT and MacOS, and 8/24 on Linux.
No longer blocks: 10575
This bug is still marked as a JavaScript issue at:
http://www.mozilla.org/projects/seamonkey/release-notes/m12-detail.html#general_browser

Re-opening to get this oversight covered.
Severity: major → normal
Status: VERIFIED → REOPENED
Priority: P1 → P3
Resolution: FIXED → ---
NOTE: Also downgraded to reduce radar detection.
closing. Open a bug against the release note people.
Status: REOPENED → RESOLVED
Closed: 21 years ago20 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.