I’m in the process of resolving the inconsistent handling of extension capabilities between Appium and the three core browser vendors (Google, Mozilla, and Microsoft). Currently, all Appium extension capabilities are considered during the slot matching process, including the value of the ‘appium:options’ object. However, all extension capabilities for the three “special” vendors are ignored during the slot matching process. My intent is to resolve this inconsistent handling by defining a clear delineation between “identity” values that should be considered for slot matching and configuration options that are passed on to the Grid node without analysis.
I notice that your capabilities examples indicate that every extension capability can be migrated into your “options” object, but the scheme I’m implementing will ignore the value of this object for slot matching (i.e. - treat the properties in the object as configuration options, not “identity” values). All extension capabilities other than 'appium: options will still be considered for slot matching.
Has the current slot matching behavior created challenges in Selenium 4 Grid configurations that would be alleviated by this proposed change?