Fix w3c capabilities in handshake

[KazuCocoa]

This is a

• Bug report
• Question
• Feature Request

Summary

Should fix w3c desired capabilities.

• Selenium : https://github.com/SeleniumHQ/selenium/blame/07a18746ff756e90fd79ef253a328bd7dfa9e6dc/rb/lib/selenium/webdriver/remote/bridge.rb

        def merged_capabilities(oss_capabilities)
          w3c_capabilities = W3C::Capabilities.from_oss(oss_capabilities)

          {
            desiredCapabilities: oss_capabilities,
            capabilities: {
              firstMatch: [w3c_capabilities]
            }
          }
        end

• Current appium
  • Curren implementation is a bit old...

            {
              desiredCapabilities: desired_capabilities,
              capabilities: {
                alwaysMatch: w3c_capabilities,
                firstMatch: [{}]
              }
            }

Environment

• ruby_lib_core version:
• Mobile platform/version/device under test:

Actual behaviour and steps to reproduce

Expected behaviour

Link to Appium/Ruby logs

Create a GIST which is a paste of your full Appium logs, and link them here.

Any additional comments

[KazuCocoa]

https://github.com/SeleniumHQ/selenium/search?utf8=✓&q=alwaysMatch&type=
is alwaysMatch removed from Ruby?

[KazuCocoa]

related with Support firstMatch #47

---

https://github.com/SeleniumHQ/selenium/blob/03bb202f3fb704d2ffca99527bfd5ffbab7dd08c/py/selenium/webdriver/remote/webdriver.py#L93
Python returns {"firstMatch": [{}], "alwaysMatch": always_match} in current master in selenium. We should fix it as well.
📝