Agreed, let's see how the primary keyboard issue shakes out. Here's a doc capturing the current status with feedback:
https://docs.google.com/a/intel.com/document/d/1L1xORKUYh7lBvJm0xykRoKHaBd4x8e95EYFe11XJ9Zw On 7 June 2016 at 15:36, Kenneth Rohde Christiansen <kenneth.christian...@gmail.com> wrote: > I would say yes as the virtual keyboard is available, but I guess that > depends on interpretation. If we want to expose additional features (say > keyboard layout) in the future then we probably need to return null here as > we can probably only get that info when the keyboard is visible. > > Kenneth > > On Tue, Jun 7, 2016 at 2:16 PM Staudinger, Robert > <robert.staudin...@intel.com> wrote: >> >> On 7 June 2016 at 13:41, Kenneth Rohde Christiansen >> <kenneth.christian...@gmail.com> wrote: >> > No, it would return a keyboard with isPhysical being false :-) >> > >> > The things is, a primary keyboard can be physical (2 in 1 attached or >> > fixed >> > physical keyboard) or virtual (tablets, which might have bluetooth >> > physical >> > keyboards) >> >> Well but in tablet mode, without a physical one being active and >> without a virtual one being displayed, getPrimaryKeyboard() would >> still return something? -- Intel GmbH - Registergericht Muenchen HRB 47456 - Dornacher Strasse 1, 85622 Feldkirchen, Germany _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
