Bill McCloskey [inactive unless it's an emergency] (:billm) Reporter
	Description • 10 years ago

The design we want is probably something like this:
1. If a content process or a plugin process wants to reload plugins, it asks the chrome process to do so.
2. If the chrome process reloads plugins and finds new ones, it broadcasts them to all content processes.

	Bill McCloskey [inactive unless it's an emergency] (:billm) Reporter
	Comment 2 • 10 years ago

Benjamin, can you explain why you think this is a dupe of bug 1096203?

	Benjamin Smedberg
	Comment 3 • 10 years ago

Plugins bundled as part of addons are registered "late", after Firefox has started up. I concluded that we had already created the content process by that point and therefore the new plugin registration wasn't being sent over properly, which would be fixed by this bug.

	Pin Zhang [:pzhang] (inactive)
	Comment 4 • 9 years ago

Hi Benjamin, I tried the latest Nightly (39.0a1 2015-03-24), it seems that both the bug 1096203 and bug 1081991 are fixed. Does it mean this bug has been fixed already by some other bug(s) fixing?

	Benjamin Smedberg
	Comment 5 • 9 years ago

I don't know. Please ask the people who fixed those bugs.

	Pin Zhang [:pzhang] (inactive)
	Comment 6 • 9 years ago

(In reply to Pin Zhang [:pzhang] from comment #4)
> Hi Benjamin, I tried the latest Nightly (39.0a1 2015-03-24), it seems that
> both the bug 1096203 and bug 1081991 are fixed. Does it mean this bug has
> been fixed already by some other bug(s) fixing?

Hi Bill, should we close this bug?

	Bill McCloskey [inactive unless it's an emergency] (:billm) Reporter
	Comment 8 • 9 years ago

I don't think we should close this. There's still work to be done afaik. It sounds like your bugs were not related to this bug. I suspect bug 1083281 might have fixed your problem.

	Pin Zhang [:pzhang] (inactive)
	Comment 9 • 9 years ago

Thanks.

	Brad Lassey [:blassey] (use needinfo?)
	Comment 10 • 8 years ago

billm, is this still relevant?

	Bill McCloskey [inactive unless it's an emergency] (:billm) Reporter
	Comment 11 • 8 years ago

I think so.

	Brad Lassey [:blassey] (use needinfo?)
	Comment 12 • 8 years ago

Bill and Benjamin, should we close this? or do something with it?

	Benjamin Smedberg
	Comment 13 • 8 years ago

This is still behind several user-visible regressions such as bug 1247042.

	Benjamin Smedberg
	Comment 14 • 8 years ago

ddurst, this should perhaps be on our plugin-work radar. It's not part of the test pilot project, but it's an e10s regression that could be a problem if there's a 0-day Flash update.

	David Durst [:ddurst]
	Comment 15 • 8 years ago

Indeed. Going to block 1282484 because I can't imagine it won't come up. (We probably need a wider meta bug for all this related work.)

	Benjamin Smedberg
	Comment 17 • 7 years ago

Related: test_refresh_navigator_plugins doesn't work with e10s because of this same underlying issue.

	Sylvestre Ledru [:Sylvestre]
	Comment 18 • 6 years ago

Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

	Sylvestre Ledru [:Sylvestre]
	Comment 19 • 6 years ago

Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information

	BMO Automation
	Comment 20 • 3 years ago

Resolving as wont fix, plugin support deprecated in Firefox 85.