Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.x] FTR: add chromium-based Edge browser support (#61684) #63063

Merged
merged 1 commit into from
Apr 9, 2020

Conversation

dmlemeshko
Copy link
Member

Backports the following commits to 7.x:

* bump dependency, add edge support in ftr services

* add config files

* fix browser version for msedge

* use npm ms-chromium-edge-driver

* download edge driver aside from session creation

* move dependency to dev

* update dist/index file

* bump edge-driver version

* change type to msedge to match w3c spec

* fix discover tests for Edge

* Revert "fix discover tests for Edge"

This reverts commit 87e7fdd.

* bump driver version up

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@dmlemeshko dmlemeshko merged commit 13baf75 into elastic:7.x Apr 9, 2020
dmlemeshko added a commit that referenced this pull request Apr 15, 2020
…#63462)

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
dmlemeshko added a commit that referenced this pull request Apr 15, 2020
…63063) (#63485)

* Revert "FTR: add chromium-based Edge browser support (#61684) (#63068)"

This reverts commit e8caa06.

* update lock file
tsullivan added a commit to tsullivan/kibana that referenced this pull request Apr 15, 2020
…edge-support

[7.7] Revert FTR: add chromium-based Edge browser support (elastic#61684) (elastic#63063)
@dmlemeshko dmlemeshko deleted the backport/7.x/pr-61684 branch January 31, 2022 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants