Closed Bug 768521 Opened 12 years ago Closed 9 years ago

Soft-blocking pop-up window appears in the runtime when soft-block is specified - no pop-up should appear

Categories

(Firefox Graveyard :: Webapp Runtime, defect, P2)

x86_64
Windows 7
defect

Tracking

(firefox16 wontfix, firefox40 fixed)

RESOLVED FIXED
Firefox 40
Tracking Status
firefox16 --- wontfix
firefox40 --- fixed

People

(Reporter: eviljeff, Assigned: nick)

References

Details

Attachments

(3 files)

If you have a plugin that's on the blocklist, (Java SE6 U29 in my case) then the block dialog pops up in the app after a short while.   

This seems to happen for every app while, as a I understand it, the plugin shouldn't be available anyway.
(In reply to Andrew Williamson [:eviljeff] from comment #0)
> Created attachment 636762 [details]
> screenshot of block dialog
> 
> If you have a plugin that's on the blocklist, (Java SE6 U29 in my case) then
> the block dialog pops up in the app after a short while.   
> 
> This seems to happen for every app while, as a I understand it, the plugin
> shouldn't be available anyway.

Isn't this expected behavior for the blocklist?

We're doing blocks on a per app basis (each app has it's own blocklist), which is likely why you are getting the prompt for every single app. Should we do a one-time only prompt for the runtime as a whole? Manage the blocklist on the runtime at a high-level, instead of a per-app basis?
I'm not sure the best solution on the blocklist being per app or per runtime - I'd favour one per runtime.  

But in this case its more that in bug 755554 its specified that only Flash will be available in the runtime but we're asking the user if they want to block Java instead.
(In reply to Andrew Williamson [:eviljeff] from comment #2)
> I'm not sure the best solution on the blocklist being per app or per runtime
> - I'd favour one per runtime.  

I'll change the title to reflect that then.

> 
> But in this case its more that in bug 755554 its specified that only Flash
> will be available in the runtime but we're asking the user if they want to
> block Java instead.

That's a separate bug - we're planning disabling all plugins except flash in the runtime. See bug 755554.
Summary: plugin blocklist dialog pops up for every app → Plugin blocklist should be managed at the runtime-level, not on a per-app basis
Switching the bug back to its original intention per today's discussion - the soft-block UI should not be coming up at all in the runtime, as there's no concept of soft-blocking plugins in the desktop runtime.
Summary: Plugin blocklist should be managed at the runtime-level, not on a per-app basis → Soft-blocking pop-up window appears in the runtime when soft-block is specified - no pop-up should appear
Alex or Jorge - How often have we soft-blocked flash? We're trying to figure out how often this bug could occur in the web runtime in order to prioritize this bug.
We soft-blocked some old versions of Flash a few months ago, and we considered doing a similar thing more recently (and didn't in the end). Flash is so prevalent that any kind of block is a massive and disruptive action, so we do it very sparingly.
QA Contact: jsmith
Priority: -- → P1
Why the popup shouldn't appear? Should we disable without telling the user?
(In reply to Marco Castelluccio [:marco] from comment #7)
> Why the popup shouldn't appear? Should we disable without telling the user?

As jsmith notes in comment 4, there's no concept of soft-blocking plugins in the runtime.  A plugin is either blocked or it isn't.

Also note that most plugins are disabled by default anyway, so blocking only matters for the (single) plugin that isn't disabled (Flash).
Whiteboard: DesktopWebRT2
Whiteboard: DesktopWebRT2
Blocks: 1111077
Priority: P1 → P2
(In reply to Myk Melez [:myk] [@mykmelez] from comment #8)
> Also note that most plugins are disabled by default anyway, so blocking only
> matters for the (single) plugin that isn't disabled (Flash).

In bug 1122780, \n saw this dialog for Silverlight, so perhaps this doesn't only matter for Flash.
Assignee: nobody → nick
No longer blocks: 1131368
It seems to me that when pref "plugin.allowed_types" is set, we should not be doing background checks for deprecated plugins that aren't on the whitelist.  See also [0].

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=755554#c2
Depends on: 75551
Depends on: 755551
No longer depends on: 75551
John, any idea how the plugin update check code works (or where in the tree it is)?  As per my comment [0], I think we'll need to hook up that code to the whitelist you implemented in 755551.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=755551#c19
Flags: needinfo?(john)
Flags: needinfo?(john)
Attached patch patch.txtSplinter Review
Attachment #8568027 - Flags: review?(myk)
I seem to be unable to install apps in nightly currently.  Is this a known issue?
Comment on attachment 8568027 [details] [diff] [review]
patch.txt

This will work.  Just note that the pref was added in bug 1038145 for the purpose of suppressing the dialog during automated tests, so this is a new kind of use of it.  And thus it's in more danger of breaking, especially without automated tests of its own.  I won't require those here, given the sorry state of our test harness, but please file a followup to implement an automated test and another followup to enable the dialog in the runtime (for the edge case of a user who uses apps without using Firefox).
Attachment #8568027 - Flags: review?(myk) → review+
Whiteboard: [checkin-needed]
https://hg.mozilla.org/mozilla-central/rev/40dffb361899
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 40
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: