Alternative property name for browserCapabilities?

[dan.j.allen]

I understand the the W3C (or Selenium) has adopted the term "browserCapabilities" for the string that identifies a browser based on the coordinates of name, version and platform. However, I think this property name is too formal (and awkward) to expose to our users.

I recommend adding the shorthand "browser" that maps to the same configuration setting.

<extension qualifer="webdriver">
    <property name="browser">firefox</property>
</extension>

We can detect if both forms are present and throw an exception if that occurs.

WDYT? Should I file an issue?

[lfryc]

I think original purpose of browserCapabilities naming was conceptual mapping to BrowserCapabilities object in WebDriver API.

+1 I'm all for renaming it as you suggest as I never understand why we have to expose such a "complex" configuration name to user

[dan.j.allen]

Issue filed: https://issues.jboss.org/browse/ARQ-1209