Closed
Bug 282106
Opened 20 years ago
Closed 11 years ago
Need ability to reliably disable full page plugins
Categories
(Core Graveyard :: Plug-ins, defect, P1)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
WONTFIX
mozilla1.8beta1
People
(Reporter: bugs, Assigned: bugs)
References
Details
Attachments
(1 file, 2 obsolete files)
3.29 KB,
patch
|
jst
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
Using the pref plugin.disable_full_page_plugin_for_types, disable full page plugin for the specified types. This needs to be implemented in the plugin host impl for reliability.
Assignee | ||
Comment 1•20 years ago
|
||
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Flags: blocking-aviary1.1+
Priority: -- → P1
Target Milestone: --- → mozilla1.8beta1
Assignee | ||
Updated•20 years ago
|
Attachment #174198 -
Flags: review?(jst)
Comment 2•20 years ago
|
||
Comment on attachment 174198 [details] [diff] [review] patch + if (overrideTypes.IsEmpty() || !FindInReadable(mimeType, start, end)) { No need for the IsEmpty() check there, if the string is empty FindInReadable() won't find what you're looking for anyways. r+sr=jst
Attachment #174198 -
Flags: superreview+
Attachment #174198 -
Flags: review?(jst)
Attachment #174198 -
Flags: review+
Comment 3•20 years ago
|
||
won't this disable text/x-foobar even if the list only contains text/x-foo?
Assignee | ||
Comment 4•19 years ago
|
||
ok, how about this (assuming a more rigidly delimited list)
Attachment #174198 -
Attachment is obsolete: true
Attachment #175066 -
Flags: superreview?(jst)
Attachment #175066 -
Flags: review?(jst)
Comment 5•19 years ago
|
||
maybe it would be more user-friendly to pre- and append the , in the code instead of requiring it to be present in the pref? then again, probably few people will set it manually... also, Append(',')/Assign(',') is probably a bit cheaper than AssignLiteral
Assignee | ||
Comment 6•19 years ago
|
||
still, wouldn't hurt to have it in the same csv format as everything else, so here's a revised version with the 1,2,3 format reinstated.
Assignee | ||
Updated•19 years ago
|
Attachment #175066 -
Attachment is obsolete: true
Attachment #175084 -
Flags: superreview?(jst)
Attachment #175084 -
Flags: review?(jst)
Assignee | ||
Updated•19 years ago
|
Attachment #175066 -
Flags: superreview?(jst)
Attachment #175066 -
Flags: review?(jst)
Assignee | ||
Updated•19 years ago
|
Attachment #174198 -
Flags: superreview+
Attachment #174198 -
Flags: review+
Comment 7•19 years ago
|
||
That patch doesn't seem to handle changes in the preference value... Also, given that this code relies on this preference, it would make sense to move the code that changes the preference (i.e. disables or enables a plugin for a given type) into the plugin manager as well. That would also make it easier to implement disabling some plugin altogether...
Assignee | ||
Comment 8•19 years ago
|
||
This function seems to be called every time content of a type that cannot be handled internally is loaded, so no dynamic-ness was required.
Comment 9•19 years ago
|
||
It is? What's the callstack? That seems very wrong.
Assignee | ||
Comment 10•19 years ago
|
||
Oh, sorry, my bad. It happens once per session only. When my UI unsets the default handling, I remove the plugin category handler using the category manager. An API for plugin enabling would be useful, but I think that's slightly separate from this bug.
Comment 11•19 years ago
|
||
Please document the dependency on the UI in this code (and file a followup bug to remove said dependancy).
Comment 12•19 years ago
|
||
Comment on attachment 175084 [details] [diff] [review] patch r+sr=jst
Attachment #175084 -
Flags: superreview?(jst)
Attachment #175084 -
Flags: superreview+
Attachment #175084 -
Flags: review?(jst)
Attachment #175084 -
Flags: review+
Comment 13•19 years ago
|
||
Just to elaborate on comment 11, Firefox is not the only user of the plugin manager, so we shouldn't have proper behavior of the plugin manager depending on the Firefox UI...
Updated•19 years ago
|
Flags: blocking-aviary1.5+ → blocking-aviary2.0?
Comment 14•19 years ago
|
||
Let's get this sorted out/landed.
Flags: blocking-firefox2? → blocking1.8.1+
Comment 15•18 years ago
|
||
Approaching b1 - not clear why we need this. JST nom that patch if appropriate for 1.8.1
Flags: blocking1.8.1+ → blocking1.8.1-
Comment 16•18 years ago
|
||
(In reply to comment #15) > Approaching b1 - not clear why we need this. Bug 306867 is a much better one to fix, IMO, as it allows the policy to be on the plugin side. The plugin should obviously know better which files it should handle in "full screen" mode.
Comment 17•18 years ago
|
||
Bastien, this bug is about the _user_ choosing to handle a particular kind of data with a helper app instead of a plug-in. It has nothing to do with bug 306867, which is a technical issue.
Updated•14 years ago
|
Flags: blocking1.9.0.19?
Updated•14 years ago
|
Flags: blocking1.9.0.19?
Updated•14 years ago
|
Flags: blocking1.9.0.19?
Updated•13 years ago
|
Flags: blocking1.9.0.19?
Updated•13 years ago
|
Flags: blocking1.8.1-
Comment 18•11 years ago
|
||
I really don't think this is worth fixing. Users have the ability to disable the plugin altogether (using the addon manager), but I don't think the complexity of trying to configure fullpage separately from that is worth the complexity of code.
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
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
•