-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Page opened through the driver lost field focus #394
Comments
I cannot reproduce this:
|
Sorry to come back to you but your test is not enough. Can you just open the page https://www.google.ca with Firefox and look that the input field have the focus. Do you have the focus on the input field (I talk visually) ? FF: 50.0.2 Thanks |
Yes, as is proven by my snippet. |
No your script prove just that document.activeElement return to you the input. Try this: In the case 2 I expect to have an array who contain one element, the same as the first call. It's very simple to verify in fact. Just open the page with m.navigate("https://www.google.ca") Can you explain me ? Thanks |
OK, I think you are right that It seems that the root cause is that we somehow focus the address bar after opening the first window. To ensure proper focus is given to the web content frame (the I filed bug 1328676 to fix this. |
I've a very large test suite to test pretty all features expected for selenium if you want ;) |
…g; r=automatedtester When a new Marionette session is started, the web content frame (currently selected <xul:browser> element) is not in focus, causing issues such as mozilla/geckodriver#394. This changes the current web content to be selected upon top-level browsing context navigation and the creation of new sessions. MozReview-Commit-ID: EgG9gRHtwOA --HG-- extra : rebase_source : 79c89e2a6d35badf454645bbfb5197a94bb1f980
…g. r=automatedtester, a=test-only When a new Marionette session is started, the web content frame (currently selected <xul:browser> element) is not in focus, causing issues such as mozilla/geckodriver#394. This changes the current web content to be selected upon top-level browsing context navigation and the creation of new sessions. MozReview-Commit-ID: EgG9gRHtwOA --HG-- extra : source : 8c25f4454f5bf48257416a1443cd715d44bdd492
This has now landed on Nightly (53) and Aurora/ESR (52). |
…g; r=automatedtester When a new Marionette session is started, the web content frame (currently selected <xul:browser> element) is not in focus, causing issues such as mozilla/geckodriver#394. This changes the current web content to be selected upon top-level browsing context navigation and the creation of new sessions. MozReview-Commit-ID: EgG9gRHtwOA
…g; r=automatedtester When a new Marionette session is started, the web content frame (currently selected <xul:browser> element) is not in focus, causing issues such as mozilla/geckodriver#394. This changes the current web content to be selected upon top-level browsing context navigation and the creation of new sessions. MozReview-Commit-ID: EgG9gRHtwOA
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue. |
Firefox Version
50.0.2
Platform
Linux
Steps to reproduce -
Open a page with Firefox where a field in a form have the focus by default ex: https://www.google.ca
(the search input have the focus)
Open the same page through the driver and the focus is not here.
The text was updated successfully, but these errors were encountered: