Closed Bug 1517196 Opened 6 years ago Closed 6 years ago

Invalid frame id doesn't cause a "no such frame" error to be raised


(Remote Protocol :: Marionette, defect, P1)



(firefox-esr60 unaffected, firefox64 wontfix, firefox65 wontfix, firefox66 fixed)

Tracking Status
firefox-esr60 --- unaffected
firefox64 --- wontfix
firefox65 --- wontfix
firefox66 --- fixed


(Reporter: whimboo, Assigned: whimboo)


(Blocks 1 open bug, )



(3 files, 1 obsolete file)

Originally filed as:

When accessing the endpoint `session/048b061c-fae2-624c-b701-72c2e9f24b05/frame` and passing in an invalid frame id, we currently raise an invalid argument error.

This is most likely a regression from switching to serde (bug 1396821). We should fix it in the 0.24 release of geckodriver.
This might actually be a bug in the spec. Lets follow up on the Github issue for now until it is clear.
Whatever solution we need, what we clearly miss are wdspec tests, which I will have to write here.

Also I noticed a bug in the webdriver rust unit tests, which will be fixed as a ride-along.

We actually will update the WebDriver specification to fix this particular failure. As such lets write some wdspec tests to make sure we cover those invalid data type cases.

Assignee: nobody → hskupin
Blocks: webdriver
Priority: -- → P1

Sounds great. I hope Google is committed to changing chromedriver
and that this doesn’t cause any user script regression, i.e. that
no one is relying on this behaviour in their tests.

Yes, we are going to change it. As such I filed Sadly my PR was merged too early, which caused two remaining items to be left-over. Those will be fixed with

If the frame id argument of the "Switch To Frame" command is
a web element, but not a valid frame object, an "invalid argument"
error needs to be thrown instead of a "no such frame" error.
Attachment #9035063 - Attachment is obsolete: true
Component: geckodriver → Marionette
Pushed by
[marionette] Raise "no such element" error in "Switch To Frame" for unknown elements. r=ato
[geckodriver] Fix unit test for invalid frame id. r=ato
[wdspec] Add tests for "Switch To Frame" command. r=ato
Created web-platform-tests PR for changes under testing/web-platform/tests

Is this something which requires Beta backport or can it ride the trains?

Flags: needinfo?(hskupin)
Flags: in-testsuite+

It's not a regression, and I don't think that we have to uplift it to beta due to the code paths are rarely used.

Flags: needinfo?(hskupin)
Keywords: regression
No longer blocks: 1495062
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.