Skip to content

feat(options): make axe.ping configurable with pingWaitTime#3273

Merged
WilcoFiers merged 2 commits intodevelopfrom
disable-axe-ping
Nov 12, 2021
Merged

feat(options): make axe.ping configurable with pingWaitTime#3273
WilcoFiers merged 2 commits intodevelopfrom
disable-axe-ping

Conversation

@WilcoFiers
Copy link
Copy Markdown
Contributor

  • Document the existence of pingWaitTime
  • Have pingWaitTime: 0 skip the ping step altogether

Closes issue: #3272

@WilcoFiers WilcoFiers requested a review from a team as a code owner November 11, 2021 13:14
@WilcoFiers WilcoFiers merged commit ce4dfaf into develop Nov 12, 2021
@WilcoFiers WilcoFiers deleted the disable-axe-ping branch November 12, 2021 16:52
@scurker
Copy link
Copy Markdown
Contributor

scurker commented Nov 12, 2021

Just so I follow:

Setting pingWaitTime to 0 means that only an axe.run is sent? Is this making the assumption that we're re-implementing a ping in the axe extension to first validate that we can communicate with a frame?

My concern lies that if only a single call is made, we don't want to wait 60000ms to timeout if the frame is unable to communicate. We can implement our own ping method in the extension that encompasses both, but just FYI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants