Support for Native Browser Events

[brian-mann]

TBD - write the reasoning and process behind achieving this.

[brian-mann]

With the release of Chrome 63 we can now finally do this.

We'll begin by adding { native: true } to existing commands for users to opt into using the native variants of them.

From there we'll add new commands for file uploads, etc.

We can also expose a low level command for talking directly to the debugger protocol to expose all of the other power and goodness that extends well beyond WebDriver.

[brian-mann]

With the release of Chrome 63 we can now finally do this.

We'll begin by adding { native: true } to existing commands for users to opt into using the native variants of them.

From there we'll add new commands for file uploads, etc.

We can also expose a low level command for talking directly to the debugger protocol to expose all of the other power and goodness that extends well beyond WebDriver.

[bahmutov]

👏👍🎉

…

Sent from my iPhone

On Oct 26, 2017, at 18:56, Brian Mann ***@***.***> wrote: With the release of Chrome 63 we can now finally do this. We'll begin by adding { native: true } to existing commands for users to opt into using the native variants of them. From there we'll add new commands for file uploads, etc. We can also expose a low level command for talking directly to the debugger protocol to expose all of the other power and goodness that extends well beyond WebDriver. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[bahmutov]

👏👍🎉

…

Sent from my iPhone

On Oct 26, 2017, at 18:56, Brian Mann ***@***.***> wrote: With the release of Chrome 63 we can now finally do this. We'll begin by adding { native: true } to existing commands for users to opt into using the native variants of them. From there we'll add new commands for file uploads, etc. We can also expose a low level command for talking directly to the debugger protocol to expose all of the other power and goodness that extends well beyond WebDriver. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[mateatslc]

good news, sounds exciting! 👏

[mateatslc]

good news, sounds exciting! 👏

[dziamid]

Awesome! Is it devtools compatible? Do you plan to eventually deprecate the not-native commands?

[dziamid]

Awesome! Is it devtools compatible? Do you plan to eventually deprecate the not-native commands?

[brian-mann]

It is dev tools compatible.

We will definitely not ever deprecate the non-native commands because they are actually more precise (as long as they work correctly). Non native can be issued synchronously and it's impossible to miss coordinates.

Native events will always be async, so if we ask for them to fire at a specific coordinate, it will take take before it's actually issued. If there are state changes by then - you have a failure.

We'll likely have a few native commands only like .attach() or something. But then enable you to opt into the native commands for commands we already have.

[brian-mann]

It is dev tools compatible.

We will definitely not ever deprecate the non-native commands because they are actually more precise (as long as they work correctly). Non native can be issued synchronously and it's impossible to miss coordinates.

Native events will always be async, so if we ask for them to fire at a specific coordinate, it will take take before it's actually issued. If there are state changes by then - you have a failure.

We'll likely have a few native commands only like .attach() or something. But then enable you to opt into the native commands for commands we already have.

[dwelle]

Does this mean we'll able to invoke and test :hover/:active pseudo classes?

[dwelle]

Does this mean we'll able to invoke and test :hover/:active pseudo classes?

[brian-mann]

Yes

[brian-mann]

Yes

[zth]

Is there a plan to integrate file uploading better with native events landing? There's a comment about it here cut I cannot seem to find any more information about it.

[zth]

Is there a plan to integrate file uploading better with native events landing? There's a comment about it here cut I cannot seem to find any more information about it.

[atomboulian]

My question is the same as @zth. Seems like this would be true, but I just want to confirm. There are medium articles talking about file uploads not being supported, even in February of this year.

[atomboulian]

My question is the same as @zth. Seems like this would be true, but I just want to confirm. There are medium articles talking about file uploads not being supported, even in February of this year.

[jpike88]

Just curious where things are at? I can't get a good reading on how close this functionality is to being ready or if it is already available

[jpike88]

Just curious where things are at? I can't get a good reading on how close this functionality is to being ready or if it is already available

[brian-mann]

@Bkucera is starting on this work this week. We've gone through the game plan and will begin implementing this and all of the other work orthogonal to native events.

[brian-mann]

@Bkucera is starting on this work this week. We've gone through the game plan and will begin implementing this and all of the other work orthogonal to native events.

[egucciar]

@brian-mann will this change some of the known "permanent limitations" of Cypress? One example being something like performance testing, which with integration with Dev Tools could totally be within reach

[egucciar]

@brian-mann will this change some of the known "permanent limitations" of Cypress? One example being something like performance testing, which with integration with Dev Tools could totally be within reach

[brian-mann]

@egucciar yes, that page is a bit outdated now. I wouldn't say it's really native events per-se, we've known about them and tapped into the early parts of them for awhile, it has to do with the underlying architectural model and the proxy layer that cypress sits in.

There are a handful of things that all together will improve that and mean that Cypress will be a bit more transparent so your application behaves more closely to how it operates outside of Cypress. It's a bit like the uncertainty principle that by inspecting and viewing "the truth" of what happens in the browser in order to model and predict it, we thereby end up changing its behavior. Performance testing bit further outside-in than how Cypress operates, and because of that, our presence changes the behavior.

It is certainly possible for us to change even that - because the tools already exist, but it's more of a documentation / process problem for us. We're really good at one thing, and attempting to do too many things (even those closely related) is difficult while also maintaining a clear and specific objective.

[brian-mann]

@egucciar yes, that page is a bit outdated now. I wouldn't say it's really native events per-se, we've known about them and tapped into the early parts of them for awhile, it has to do with the underlying architectural model and the proxy layer that cypress sits in.

There are a handful of things that all together will improve that and mean that Cypress will be a bit more transparent so your application behaves more closely to how it operates outside of Cypress. It's a bit like the uncertainty principle that by inspecting and viewing "the truth" of what happens in the browser in order to model and predict it, we thereby end up changing its behavior. Performance testing bit further outside-in than how Cypress operates, and because of that, our presence changes the behavior.

It is certainly possible for us to change even that - because the tools already exist, but it's more of a documentation / process problem for us. We're really good at one thing, and attempting to do too many things (even those closely related) is difficult while also maintaining a clear and specific objective.

[egucciar]

@brian-mann appreciate the detailed explanation! So in short though this may open up the possibility of further integrations, some use cases still may not be applicable due to the overall architecture, performance testing being one of those things. Makes perfect sense.

[egucciar]

@brian-mann appreciate the detailed explanation! So in short though this may open up the possibility of further integrations, some use cases still may not be applicable due to the overall architecture, performance testing being one of those things. Makes perfect sense.

[brian-mann]

Updates: along with native events, this goes hand in hand with cross browser support, which I added an update for here: #310 (comment)

TLDR; we are adding cross browser support as a major priority here. Work has been going on for months and we're ready to begin implementation.

[brian-mann]

Updates: along with native events, this goes hand in hand with cross browser support, which I added an update for here: #310 (comment)

TLDR; we are adding cross browser support as a major priority here. Work has been going on for months and we're ready to begin implementation.

[pvdyck]

@bahmutov ready for Sprint 5 or postpone ?

[pvdyck]

@bahmutov ready for Sprint 5 or postpone ?