Op 08-06-2023 om 05:41 schreef Mathias Bynens:
In ChromeDriver, we don’t have feature flags per se. Instead the mechanism we have available is vendor-prefixed command mappings <https://source.chromium.org/chromium/chromium/src/+/main:chrome/test/chromedriver/server/http_handler.cc;l=206-209;drc=bdbfa8b9c04dbe680cbfb24f7ef81278c7be2604>. Features that aren’t considered stable / have received cross-vendor buy-in should not land as an unprefixed WebDriver endpoint.
I'm wondering how this would interact with WPT's testdriver.js. Assuming an RFC has been sent and a new testdriver command is added, there's only one dispatcher for WebDriver commands. Furthermore, when should the WPT code start trying to use the unprefixed command assuming that would vary across milestones?
-- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/449784bd-dc64-f338-8adc-db415fff0932%40intel.com.
