Closed
Bug 544910
Opened 15 years ago
Closed 14 years ago
[OOPP] in private browsing mode killed plugin area is not invalidated
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: kbrosnan, Unassigned)
References
Details
1. Put Firefox in private browsing mode 2. load some plugin content 3. kill the mozilla-runtime process Expected results: plugin area invalidated (shows as a black square) Currently plugin content is shown but the user is not able to interact with it. Switching in and out of the tab invalidates the plugin area.
Comment 1•14 years ago
|
||
Not sure what to tell you, but the new Plugin UI code just landed, so we now should see in content plugin ui when it crashes or get's task killed, instead of just black squares. I believe some of the black square issues are gone now too. Testing with Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a2pre) Gecko/20100212 Minefield/3.7a2pre (.NET CLR 3.5.30729) ID:20100212145610 For example, If I kill all mozilla-runtime(s) on windows for youtube, the new plugin crashed ui comes up, and i can try and reload the page from the new in content plugin ui, which reloads the page, the plugin comes back, but the plugin still doesn't play. Did you you a specific build you were testing?
Comment 2•14 years ago
|
||
On second thought, you might also be seeing bug 545686 on some sites. Was there a specific site where you were just seeing black squares?
Reporter | ||
Comment 3•14 years ago
|
||
This was before the crash handler was fully operational. Tested it with Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a2pre) Gecko/20100215 Minefield/3.7a2pre / http://hg.mozilla.org/mozilla-central/rev/38929916c6d1 and the crash handler appears.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•