Intermittent /webdriver/tests/bidi/input/perform_actions/navigation.py | test_pointer - webdriver.bidi.error.UnknownErrorException: unknown error ([Exception... "(null)" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"])
Categories
(Remote Protocol :: WebDriver BiDi, defect, P5)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: intermittent-failure, intermittent-testcase)
This is a new test as introduced with my work on bug 1921314. It shows that when a navigation happens while we are in the middle of checking if the given target is in the currently visible viewport:
0:16.51 pid:25370 1731074644864 Marionette TRACE Dispatch PointerMoveAction mouse with id: pointer-0 x: 200 y: 200
0:16.52 pid:25370 1731074644867 RemoteAgent DEBUG WebDriverBiDiConnection cb54b1c5-4b6e-4e84-82a3-82615245ac5b <- {"type":"error","id":4,"error":"unknown error","message":"[Exception... \"(null)\" nsresult: \"0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)\" location: \"JS frame :: chrome://remote/content/shared/webdriver/Actions.sys.mjs :: assertTargetInViewPort :: line 3092\" data: no]","stacktrace":"assertTargetInViewPort@chrome://remote/content/shared/webdriver/Actions.sys.mjs:3092:29\n#assertInViewPortFromContent@chrome://remote/content/webdriver-bidi/modules/windowglobal/input.sys.mjs:52:17\ndispatch@chrome://remote/content/shared/webdriver/Actions.sys.mjs:1586:11\n"}
The related code in this line is:
if (x < 0 || y < 0 || x > win.innerWidth || y > win.innerHeight) {
Note that this only happens with remote.events.async.enabled turned off, which means all the action related code runs in the content process.
Here we probably want to have a more descriptive error message only because we cannot fix it when running in that mode.
|
Reporter | |
Updated•9 months ago
|
|
||
Updated•9 months ago
|
|
||
Updated•9 months ago
|
|
|
||
Updated•9 months ago
|
|
|
Reporter | |
Comment 1•9 months ago
|
||
Given that we are going to enable the async code pretty soon by default this is code we won't no longer hit unless the user turns off this new feature. Given that I haven't seen this failure for the async code path lets just ignore it. If it might happen for async in the future we can reopen the bug.
Description
•