3 interesting bugs

Hey everyone,

Ran into three interesting bugs that I thought might be worth discussing as they pertain to the specification:

Bug #1: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8073490/
This has to do with opening external applications. In Edge this causes webdriver to hang (we plan to address this) but I realized the specification doesn't really handle what happens if the tester does something that would otherwise pull the user out of the context of the browser. Not a big deal at the moment for us as we plan to just return in this case.

Bud #2: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8515651/
This covers an issue I brought up at the July F2F around the various oddball inputs. We have issues "sending keys" to these as they are somewhat special, so thoughts on this would be interesting. I'm guessing value should just be set and any relevant events fired but wanted to know thoughts.

Bug #3: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8074852/
This final one tackles which tab is active vs which webdriver tab is active. For Edge after doing a window.open() the active tab is the new tab while the webdriver tab hasn't changed (no switch to window call). If you execute a get command, the active tab will switch back to the opener which is also the webdriver active tab and then do a navigate. In Chrome it allows the get to happen in the webdriver tab without it being in focus. As this could change what a site does (being displayed vs not displayed) it seems like an interesting case to consider.

Thoughts on these? Feel free to share any bugs you all find target more gray areas of the spec, I find them interesting!

Thanks,
Clay