-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Leadfoot 2.3 is using invalid argument type for switchToFrame #1083
Comments
In the frame switching test of the 2.3 self tests, |
The problem appears to be that the tests in Server are calling some session commands that are self-correcting (if a feature flag hasn't been set yet, the command will set the flag to and try fallback logic). This can cause the tests to pass when they shouldn't, and the corresponding flags to be set to the wrong values. The next time one of the related session commands is called, it will be using the incorrect flag value. |
Another aspect this problem, and possibly the root of it, is that the frame ID check is looking for a NoSuchFrame error rather than InvalidArgument. |
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
Backport the fix for theintern/intern#1083, which fixes the handling of frame IDs in W3C compliant webdriver sessions.
This was added to leadfoot in theintern/leadfoot@0bb35b2 |
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references theintern#1083
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
The frame ID check in switchToFrame was based on an older version of the W3C spec that said drivers should return a NoSuchFrame error for an invalid ID. The current spec says to return InvalidArgument, which is what current webdrivers tend to do. references #1083
The leadfoot 'Session - frame switching' self test fails for at least Chrome 79+ and Leadfoot 2.3.0 because Session is using string IDs for frames, which isn't valid for W3C mode.
The text was updated successfully, but these errors were encountered: