NPAPI:AdvancedKeyHandlingHistory: Difference between revisions

no edit summary
(Created page with 'It took almost 10 years to finalize a spec for advanced key handling in NPAPI. This page provides information on past attempts. = Deneb Meketa, Ado…')
 
No edit summary
 
Line 1: Line 1:
It took almost 10 years to finalize a spec for [[NPAPI:AdvancedKeyHandling|advanced key handling]] in NPAPI. This page provides information on past attempts.
It took almost 10 years to finalize a spec for [[NPAPI:AdvancedKeyHandling|advanced key handling]] in NPAPI. This page provides information on past attempts.


= Deneb Meketa, Adobe, April 2002 =
= Discussions and Documentation =


== [https://bugzilla.mozilla.org/show_bug.cgi?id=93149#c15 Original Proposal] ==
<tt>Note: Some of the archive links here require authentication, however most relevant information behind those links has been copied to this document.</tt>
 
Mozilla bugs [https://bugzilla.mozilla.org/show_bug.cgi?id=78414 78414] and [https://bugzilla.mozilla.org/show_bug.cgi?id=93149 93149] have some information but are generally cluttered with useless comments. Deneb Meketa from Adobe posted a proposal on [https://bugzilla.mozilla.org/show_bug.cgi?id=93149 bug 93149], comments [https://bugzilla.mozilla.org/show_bug.cgi?id=93149#c34 #34] and [https://bugzilla.mozilla.org/show_bug.cgi?id=93149#c36 #36] discuss it.
 
There was a [https://mail.mozilla.org/private/plugin-futures/2004-March/000057.html plugin-futures discussion started by Johnny Stenback in March of 2004] on the topic of handled status for key events. Johnny's discussion resulted in a [https://intranet.mozilla.org/PluginFutures/index.php/PluginEvents plugin-futures wiki entry].
 
Aaron Leventhal of IBM started a [https://mail.mozilla.org/private/plugin-futures/2004-April/000064.html relevant discussion on plugin-futures in April of 2004]. The proposal discussed is an extension of Johnny's from March of 2004 and is actually fairly detailed.
 
API modification work is discussed in [https://bugzilla.mozilla.org/show_bug.cgi?id=348279 Mozilla bug 348279]. The discussion there generally revolves around a proposal from Sun. Sun posted to plugin-futures about this work in March of 2007.
 
Karl Tomlinson [http://groups.google.com/group/mozilla.dev.tech.plugins/browse_thread/thread/7b21b6b08499941d/5458da943ed1a81b#5458da943ed1a81b wrote a message on Google Groups proposing an X11 windowless plugin API]. There is some related info in that message.
 
Josh Aas wrote a [http://boomswaggerboom.wordpress.com/2008/09/11/npapi-plugin-bugs-accessibility/ blog post] on the issue in September of 2008.
 
= Past Proposals =
 
== Deneb Meketa, Adobe, April 2002 ==
 
=== [https://bugzilla.mozilla.org/show_bug.cgi?id=93149#c15 Original Proposal] ===


<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
Line 52: Line 70:
</tt></div>
</tt></div>


== Comments ==
=== Comments ===


Deneb Meketa responding to Peter Lubczynski:
Deneb Meketa responding to Peter Lubczynski:
Line 96: Line 114:
combinations to not reach the plugin.
combinations to not reach the plugin.


= Johnny Stenback, Mozilla, March 2004 =
== Johnny Stenback, Mozilla, March 2004 ==


== [https://mail.mozilla.org/private/plugin-futures/2004-March/000057.html Original Proposal] ==
=== [https://mail.mozilla.org/private/plugin-futures/2004-March/000057.html Original Proposal] ===


<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
Line 106: Line 124:
</tt></div>
</tt></div>


== Comments ==
=== Comments ===


One problem with this system is that it would require an accurate platform-specific specification of how the browser is supposed to interpret NPEvent data, which is often a pointer to a native structure, and often a synthesized one.
One problem with this system is that it would require an accurate platform-specific specification of how the browser is supposed to interpret NPEvent data, which is often a pointer to a native structure, and often a synthesized one.
Line 112: Line 130:
This also lacks an accurate description of how focus flow would work.
This also lacks an accurate description of how focus flow would work.


= Aaron Leventhal, IBM, April 2004 =
== Aaron Leventhal, IBM, April 2004 ==


== [https://mail.mozilla.org/private/plugin-futures/2004-April/000064.html Original Proposal] ==
=== [https://mail.mozilla.org/private/plugin-futures/2004-April/000064.html Original Proposal] ===


<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
Line 148: Line 166:
</tt></div>
</tt></div>


== Comments ==
=== Comments ===


Rudi Sherry:
Rudi Sherry:
Line 170: Line 188:
This doesn't cover the case of windowed plugins on Linux and Windows. The focus event enum in the spec adds cases for Carbon Mac OS X events.
This doesn't cover the case of windowed plugins on Linux and Windows. The focus event enum in the spec adds cases for Carbon Mac OS X events.


= Oliver Yeoh and Danielle Pham, Sun, September 2007 =
== Oliver Yeoh and Danielle Pham, Sun, September 2007 ==


== [https://bugzilla.mozilla.org/show_bug.cgi?id=348279 Original Proposal] ==
=== [https://bugzilla.mozilla.org/show_bug.cgi?id=348279 Original Proposal] ===


<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
<div style="width:99.5%; margin:0 auto; padding: 5px; background-color:#E0E0E0; border:1px dashed #000000"><tt>
Line 353: Line 371:
</tt></div>
</tt></div>


== Comments ==
=== Comments ===


How exactly is the browser supposed to send GetFocusFirstEvent/GetFocusLastEvent events to the plugin via existing NPP_HandleEvent. NPEvent data is different on each platform, it isn't clear how that would be conveyed when, for example, the type for NPEvent is "void*", a pointer to a native event structure.
How exactly is the browser supposed to send GetFocusFirstEvent/GetFocusLastEvent events to the plugin via existing NPP_HandleEvent. NPEvent data is different on each platform, it isn't clear how that would be conveyed when, for example, the type for NPEvent is "void*", a pointer to a native event structure.
Confirmed users, Bureaucrats and Sysops emeriti
1,680

edits