The keyboard_types::webdriver module implements parts of the WebDriver spec. It is fairly distinct from the types we otherwise expose, and arguably doesn't have much to do with "keyboard types".
Furthermore, there is a lot of value in keyboard-types becoming as stable as possible, to allow the rest of the ecosystem to depend on it for interop with other crates, while the webdriver module feels like it will need more time to stabilize, see e.g. #79. Though to be honest, I haven't spent that much time on it, so maybe it's not that bad?
I searched GitHub, it seems that the only consumers of the module is afrim-preprocessor in tests and Servo.
CC @yezhizhen @PotatoCP from Servo, WDYT? Would you be amenable to moving the webdriver module to Servo instead? I suspect this would allow you to fix things faster than having it here in a separate repo which is bound by stability concerns.
CC @pythonbrad since this affects you as well.
The
keyboard_types::webdrivermodule implements parts of the WebDriver spec. It is fairly distinct from the types we otherwise expose, and arguably doesn't have much to do with "keyboard types".Furthermore, there is a lot of value in
keyboard-typesbecoming as stable as possible, to allow the rest of the ecosystem to depend on it for interop with other crates, while thewebdrivermodule feels like it will need more time to stabilize, see e.g. #79. Though to be honest, I haven't spent that much time on it, so maybe it's not that bad?I searched GitHub, it seems that the only consumers of the module is
afrim-preprocessorin tests and Servo.CC @yezhizhen @PotatoCP from Servo, WDYT? Would you be amenable to moving the
webdrivermodule to Servo instead? I suspect this would allow you to fix things faster than having it here in a separate repo which is bound by stability concerns.CC @pythonbrad since this affects you as well.