[Webkit-unassigned] [Bug 18638] Add support for non X11 unix platforms
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Apr 15 22:05:17 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=18638
--- Comment #10 from Michael Emmel <mike.emmel at gmail.com> 2012-04-15 22:05:17 PST ---
(In reply to comment #9)
> (In reply to comment #7)
> > So is there a policy on how often Webkit updates NPAPI headers ?
> > Or should i just pull that file from npapi-SDK and submit as a patch for review ?
>
> The reason you see divergence is that the npapi-sdk project is quite new in the history of NPAPI; until recently, there was no single source, and each browser vendor had their own copies of the headers that had diverged a fair amount. Work has been done to bring WebKit much closer to the new upstream header, but it was never finished (see bug 38666, bug 77200, and the various bugs they reference).
>
> I'd recommend strongly against trying to check in the upstream headers directly as a single patch, and instead pick out the differences specifically related to the MOZ_X11 guard and reconcile just those in one patch.
But why have platform types in this header ? They can readily be moved to a included platform header along with platform specific entry points.
The EGL bindings do a fairly good job of isolating platform types and can server as a template.
Where needed you have NativeDisplay. NativeWindow etc.
On top of this both WebKit and Mozilla have and extensive porting layer very few plugins actually need direct access to the underlying platform. Exporting the porting layer as a target for plugins suffices for 90% or more of the plugins. Flash for example could be trivially ported to both browsers porting layers.
With HTML 5 the api is effectively complete in the porting layer.
This is perhaps going beyond this bug report. But recognize the need of and api for native extensions that makes far more sense then the current plugin concept. Almost all plugins should be ported to a new native extension api synchronized between browsers. A small number will need to bypass this.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list