Closed
Bug 494940
Opened 16 years ago
Closed 15 years ago
Open mixed content dialog asynchronously
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: johnath, Assigned: smaug)
References
(Blocks 1 open bug)
Details
(Keywords: fixed1.9.1)
Attachments
(2 files)
6.72 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
8.03 KB,
patch
|
KaiE
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #494590 +++
We should still fix bug 494590 for real, but in the meantime, the suggestion came up to launch this particular dialog asynchronously, to avoid getting hung up in a synchronous load that results in the dialog not having any content.
Assignee | ||
Comment 1•16 years ago
|
||
Assignee: kaie → Olli.Pettay
Attachment #379739 -
Flags: review?(bzbarsky)
Assignee | ||
Updated•16 years ago
|
Flags: blocking1.9.1?
Updated•16 years ago
|
Attachment #379739 -
Flags: review?(bzbarsky) → review+
Comment 2•16 years ago
|
||
Comment on attachment 379739 [details] [diff] [review]
async alert
Looks fine, but I'd rather not use the optional arg. Just make it required and fix callers, ok?
Also, get kai to review (at least post-landing)?
Assignee | ||
Updated•16 years ago
|
Attachment #379739 -
Flags: review?(kaie)
Assignee | ||
Comment 3•16 years ago
|
||
Updated•15 years ago
|
Flags: blocking1.9.1? → blocking1.9.1+
Comment 4•15 years ago
|
||
As per comment 2, can we get this on mozilla-central at least and wait for Kaie's post-facto review before mozilla-1.9.1?
Assignee | ||
Comment 5•15 years ago
|
||
Ok, landing ASAP
Assignee | ||
Comment 6•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 7•15 years ago
|
||
Comment on attachment 379835 [details] [diff] [review]
+comments
r=kaie
I assume NS_DispatchToCurrentThread
will AddRef and the event dispatcher will Release, so the allocated nsAsyncAlert object will get freed properly.
Attachment #379835 -
Flags: review+
Updated•15 years ago
|
Attachment #379739 -
Flags: review?(kaie)
Assignee | ||
Comment 8•15 years ago
|
||
(In reply to comment #7)
> I assume NS_DispatchToCurrentThread
> will AddRef and the event dispatcher will Release, so the allocated
> nsAsyncAlert object will get freed properly.
Yup.
Comment 9•15 years ago
|
||
Right now this fix is fine, because we aren't able to cancel the load anyway (which is offered by the dialog, but the warning comes too late).
We still need to work on bug 62178 in order to notify prior to loading or block-or-allow mixed content by default.
Blocks: 62178
Comment 10•15 years ago
|
||
Right. By the time we can cancel from this dialog, we hope to have made all the necko access in Gecko happen at safe times. This fix is strictly a for-now fix.
Assignee | ||
Comment 11•15 years ago
|
||
Keywords: fixed1.9.1
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•