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
wrote:
> I would say yes as the
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 T
On 7 June 2016 at 13:41, Kenneth Rohde Christiansen
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)
We
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)
On Tue, Jun 7, 2016 at 1:35 PM Staudinger, Robert <
robert.staudin...@i
On 7 June 2016 at 13:24, Kenneth Rohde Christiansen
wrote:
> Yes, but that still doesn't make it the primary input device but instead the
> active one right.
Exactly. So getPrimaryKeyboard() could return a null value?
___
Crosswalk-dev mailing list
Cros
Yes, but that still doesn't make it the primary input device but instead
the active one right.
On a tablet with a bluetooth keyboard attached, I would call the VKB the
primary keyboard but the physical one might be the active one.
Kenneth
On Tue, Jun 7, 2016 at 1:20 PM Staudinger, Robert <
rober
On 7 June 2016 at 11:40, Kenneth Rohde Christiansen
wrote:
> OK, I see. I had expected something a bit more thought out already.
The question is hardware availability vs semantics -- what does it
mean to the operating system.
On Windows 8/10 you can go into touch mode without a change of the
dev
OK, I see. I had expected something a bit more thought out already.
Maybe model it after navigator.getGamepads, or the even newer
navigator.getVRDiaplay (which is modelled after the former somehow):
interface Keyboard {
readonly attribute boolean isConnected;
readonly attribute boolean is
On 7 June 2016 at 09:55, Kenneth Rohde Christiansen
wrote:
> Is there any design document, showing the potential APIs etc?
We are providing low level primitives that can be used in conjunction
with other APIs (gyro, rotation, ...)
The initial API is along the lines of (pseudo-idl)
interface Cro
Is there any design document, showing the potential APIs etc?
Kenneth
On Tue, Jun 7, 2016 at 9:51 AM Staudinger, Robert <
robert.staudin...@intel.com> wrote:
> == Abstract
>
> Crosswalk extension module providing low level primitives for querying
> whether the host operating system has a physica
== Abstract
Crosswalk extension module providing low level primitives for querying
whether the host operating system has a physical keyboard attached.
This information can be used by app authors to optimise application
appearance and behaviour on convertible devices such as laptop/tablet
hybrid co
11 matches
Mail list logo
