Closed Bug 1328048 Opened 8 years ago Closed 4 years ago

Plugin overlays are not displayed if plugin element is not fully in scroll view - round 2

Categories

(Core Graveyard :: Plug-ins, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: arni2033, Unassigned)

References

Details

(Keywords: regression)

>>> My Info: Win7_64, Nightly 49, 32bit, ID 20160526082509 STR_1: 0. Set Flash to "Ask to activate" or intall an obsolete version of Flash 1. Open URL [1] 2. Hold End key / rotate mouse wheel down until page is scrolled by at least by 1 screen to the bottom 3. When plugin icon appears in urlbar, press Home key STR_2: 0. Set Flash to "Ask to activate" or intall an obsolete version of Flash 1. Open URL [2] 2. Press Down key twice so that part of flash was cut off by top side of content area 3. Press F5, wait until the page finishes loading 4. Press Home key AR: A gray rectangle is displayed on the page instead of Flash ER: Some text or notification explaining why on earth Firefox created that gray rectangle > [1] http://tvzvezda.ru/news/vstrane_i_mire/content/201606111618-waas.htm > [2] data:text/html,<body style="height:10000px">Yep. Just another perfectly shaped gray rectangle designed by Dolske & co.<br><object height="200" width="200" data="https://bug1148978.bmoattachments.org/attachment.cgi?id=8675621"> Notes: 1) This bug manifests especially often when Firefox restores scroll position 2) Looking at bug 1195955, this seems like a common failure in Firefox. This is regression from bug 932832. Regression range: > http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d58545aaeab9&tochange=862cb6a1cc88@ Benjamin Smedberg [:bsmedberg]: It seems that this is a regresion caused by your change. Please have a look.
No longer blocks: 1277113
Component: Untriaged → Plug-ins
Product: Firefox → Core
Priority: -- → P3
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.