Here is a proposed patch:
https://issues.apache.org/jira/secure/attachment/12482729/TRINIDAD-2108.patch
Sorry for the odd diff, the svn EOL was not set to native for
the capabilities.xml.
I can add a none for all other browsers, but it appears that for the other
capabilities, the none is not
https://issues.apache.org/jira/browse/TRINIDAD-2108
I am proposing to add a new Agent capability for touch devices.
It would involve adding:
static public final CapabilityKey CAP_TOUCH_SCREEN =
CapabilityKey.getCapabilityKey(touchScreen, true);
To
On 6/13/11 9:22 AM, Andrew Robinson wrote:
https://issues.apache.org/jira/browse/TRINIDAD-2108
I am proposing to add a new Agent capability for touch devices.
It would involve adding:
static public final CapabilityKey CAP_TOUCH_SCREEN =
CapabilityKey.getCapabilityKey(touchScreen,
We could have it return constant strings of none, single and multiple
if that would suit our needs.
So my question is if we want one capability per-human interaction device or
multiple?
Option 1, one-per:
1. touchScreen capability
2. mouse capability
3. drawingPad capability
Option 2,
I think we should have one per device and we might eventually want to
support some keyboard-related ones as well to include differences
between real and various on-screen keyboards.
-- Blake Sullivan
On 6/13/11 10:52 AM, Andrew Robinson wrote:
We could have it return constant strings of none,
