Pipelight is named the same as the default Flash plugin
Bug #1607528 reported by
Roman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Pipelight |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Pipelight flash appears to share a name or something with the default flash plugin, meaning if one is disabled the other is not, making it impossible to, say, use a specific version in the context of a specific Firefox profile.
Revision history for this message
| Michael Müller (mqchael) wrote | #1 |
| Changed in pipelight: | |
| status: | New → Won't Fix |
To post a comment you must log in.
This is an requirement otherwise websites would not detect flash through Pipelight. We therefore can not change this without completely breaking Pipelight. Changing Pipelight is also not the correct way as the browser can indeed distinguish between Pipelight and the linux version of flash. This is a limitation of Firefox that you can only disable a plugin completely but don't have control over different versions of the same plugin. Chrome for example had this possibility.
However, you can use a separate Firefox profile together with an environment variable to achieve your goal. There is an old FAQ entry which explain how this works:
Enable it just for a specific browser (profile):
https:/