Why are file URLs excluded from the post-navigation checks?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
I came to an issue where I try to use chromedriver.exe to navigate to a file.
When I use an not existen file for example file:///c:/test/NotExistenFile.html then of course browser try's to navigate and returns ERR_FILE_NOT_FOUND but currently chromedriver.exe returns {"value":null} on navigation.
So I checked the documentation for implementation here:
https://www.w3.org/TR/webdriver2/#navigate-to
And I do not see any requirmentes for checking if local file exist.
Was it intentional ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the WebDriver 2 Navigate To section linked in the issue and compare its requirements with chromedriver.exe’s response for a nonexistent file URL. A useful outcome is a maintainer decision on whether the specification should require an error or explicitly permit the current null response.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100