Open Bug 625056 Opened 14 years ago Updated 12 years ago

Port |Bug 59314 - Alerts should be content-modal, not window-modal| to SeaMonkey

Categories

(SeaMonkey :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

      No description provided.
Blocks: FF2SM
Blocks: 625038
Depends on: 625114
This fixes bug 625038, after fixing bug 625114 too.
I'll land this when the latter is fixed only...

This code is mostly copied from FF, with some nits fixed.
The only points I wondered about:
*does the code belongs in navigator.js (and not browser.js)?
*should I s/gBrowser/getBrowser/ there?
Assignee: nobody → sgautherie.bz
Status: NEW → ASSIGNED
Attachment #503215 - Flags: review?(neil)
Comment on attachment 503215 [details] [diff] [review]
(Av1) Just port it, Remove an obsolete comment

(In reply to comment #1)
> The only points I wondered about:

And "do we need an extra check or something to be safe on the mailnews side?".
Attached patch (Bv1-FF) Fix some nits (obsolete) (deleted) — Splinter Review
Attachment #503235 - Flags: review?(dolske)
Comment on attachment 503215 [details] [diff] [review]
(Av1) Just port it, Remove an obsolete comment

This is missing a swathe of XBL changes, both tabbrowser and notificationbox.

> 
> 
Nit: don't need two consecutive blank lines

>+  let foundBrowser = gBrowser.getBrowserForDocument(aWindow.document);
[What happens if a frame alerts?]

>+            let browser = aBrowser || this.mCurrentBrowser;
Nit: should put tab here, it doesn't change between prompts.

>+                let tab = self._getTabForContentWindow(browser.contentWindow);
Someone mentioned on one of the session store bugs that we need a getTabForBrowser function (session store has an internal version) which Gavin suggested could use the uniqueID (browser.id == tab.linkedPanel).

>+                let count = parseInt(browser.getAttribute("tabmodalPromptShowing")) - 1;
Nit: The - operator already does a parse (ok, so it's a parseFloat...)

>+              listPrompts : function(aPrompt) {
[Unused parameter?]

>+                // NodeList --> real JS array
There's a function for that, although I forget it offhand.
Attachment #503215 - Flags: review?(neil) → review-
Comment on attachment 503235 [details] [diff] [review]
(Bv1-FF) Fix some nits

As far as I can see this is just nitpicky style churn.
Attachment #503235 - Flags: review?(dolske) → review-
Attachment #503235 - Attachment is obsolete: true
Blocks: 626294
Looks like Serge dropped this, and it is of HIGH value to our users, removes our DOS strike-area.

Firefox has had this feature since Fx4.

Ewong, does this look like something you'd be capable/willing to take on, (it is more advanced than your average bug)
Assignee: sgautherie.bz → nobody
Status: ASSIGNED → NEW
(In reply to comment #6)
> Looks like Serge dropped this,

Yes. Iiuc, this +/- depend(ed) on bug 625114, which in turn...
These seemed too complicated wrt my limited skill in this area.
(And I currently don't have much free time (to spend on Moz/SM) :-|)
Blocks: 736905
>>+                // NodeList --> real JS array
> There's a function for that, although I forget it offhand.
Array.slice() ?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: