[Webkit-unassigned] [Bug 77200] [npapi] Master bug to synchronize with npapi-sdk

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=77200





--- Comment #4 from Stuart Morgan <stuartmorgan at chromium.org>  2012-01-27 05:56:24 PST ---
(In reply to comment #3)
> Did I misunderstand something?

No, "the whole point" was poor word choice. npapi-sdk has a few major goals:
1) Have a single source of "truth" for these headers, which is always up to date with the latest NPAPI spec changes.
2) Give plugin developers a single source for headers that they should use in development
3) Make it easy for browser developers to maintain their headers.

The less forking there is in the browser sources, the easier 3 is for the browser vendors, thus bug 38666 and follow-ups (and all the similar work I did in Chromium).


I'm not arguing that continuing unforking is a bad idea; obviously I don't think that or I wouldn't have filed the follow-up bugs. I'm just confused about the assertion that doing so would help plugin development; given 1 and 2, plugin developers should *not* be using the WebKit project as a source of NPAPI headers. There shouldn't be any reason for anyone not maintaining the WebKit NPAPI implementation to care about WebKit's copies of these headers at this point.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.