-
Notifications
You must be signed in to change notification settings - Fork 2.3k
getCurrentUrl() protractor tests failing on Internet Explorer 11 (latest) #778
Comments
getCurrentUrl also fails for some of us in IE10 ( #132 ) |
Thanks @KasMA1990 i think #132 should be reopened then this one be closed as duplicate. |
Thanks for investigating - it's fine to track here and leave the old issue closed. |
Here's an isolated SauceLabs test just looking at the changing URL. You can see from the screenshots that the URL in the browser looks correct, but it's not returning the path: https://saucelabs.com/jobs/36b8bad2d2144e009e9fc84052b8167a Seems like an IEDriver bug. Let's make a simplified test case and report. |
Right, I agree is an IEDriver bug. I can also confirm by manually using webdriver JsonWireProtocol, e.g.
Returns an outdated url on IE. |
If someone feels like putting some time on this, take a look at selenium source:
And improve @Test
public void testShouldReportTheCurrentUrlCorrectly() {
driver.get(pages.simpleTestPage);
assertTrue(pages.simpleTestPage.equalsIgnoreCase(driver.getCurrentUrl()));
driver.get(pages.javascriptPage);
assertTrue(pages.javascriptPage.equalsIgnoreCase(driver.getCurrentUrl()));
} |
Are there any solutions or workarounds for this bug? |
Workaround is using getLocationAbsUrl() |
Ah yes, missed the () ;) |
Awesome! You guys saved this guy a big headache with IE. Many thanks and I hope to offer something useful for you in the future. |
getLocationAbsUrl() - Is supposed to work only on Angular pages ? |
@sjelin can you confirm whether this is still an issue? |
@cnishina windows |
Closing this as not reproducible. Test steps to reproduce:
|
Hi @cnishina @juliemr
same issue on browser stack IE 10 as well, however It works fine on IE 11. |
Protractor will never support / fix this because the browser is not supported by Microsoft since 2016. It's for all versions of IE (https://venturebeat.com/2016/01/12/microsoft-ends-support-for-ie8-ie9-ie10-and-windows-8/) |
I added IE11 to
/spec/multiConf.js
and I could confirm an IE issue when testing AJAX-changed urls:To recreate just run
npm test
agains IE11The tests that fails is
it('should allow a mix of using protractor and using the driver directly'
at/spec/basic/lib_spec.js
I could also recreate on TravisCI - SauceLabs during a PR:
https://travis-ci.org/angular/protractor/builds/24499725#L764
The text was updated successfully, but these errors were encountered: