Skip to content

webdriver: Fix outdated timeouts test and remove redundant check#41631

Merged
yezhizhen merged 9 commits intoservo:mainfrom
yezhizhen:go
Jan 5, 2026
Merged

webdriver: Fix outdated timeouts test and remove redundant check#41631
yezhizhen merged 9 commits intoservo:mainfrom
yezhizhen:go

Conversation

@yezhizhen
Copy link
Copy Markdown
Member

Initially the attempt is to validate params according to spec. But it turns out validation is already done at webdriver crate so I reverted the change.

But Chrome/Firefox are not compliant with spec: https://wpt.fyi/results/webdriver/tests/classic/new_session/timeouts.py?label=experimental&label=master&aligned. They only allow script timeouts to be None but not pageLoad and implicit, which is how the test is currently written.

Testing: Updated the test to be compliant with spec. New failures are because it is validated at webdriver crate.

@servo-wpt-sync
Copy link
Copy Markdown
Collaborator

🤖 Opened new upstream WPT pull request (web-platform-tests/wpt#56959) with upstreamable changes.

@yezhizhen
Copy link
Copy Markdown
Member Author

@servo-wpt-sync
Copy link
Copy Markdown
Collaborator

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#56959).

@yezhizhen yezhizhen requested a review from xiaochengh January 2, 2026 12:29
@servo-wpt-sync
Copy link
Copy Markdown
Collaborator

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#56959).

@TimvdLippe
Copy link
Copy Markdown
Contributor

If Chrome and Firefox already behave like this, I think the specification editors typically update the spec instead of the browsers. Do you have a spec issue where browser vendors indicate they agree to update the behaviour? If not, I don't think we should update the test and instead match their behaviour and update the spec.

@yezhizhen
Copy link
Copy Markdown
Member Author

yezhizhen commented Jan 3, 2026

If Chrome and Firefox already behave like this, I think the specification editors typically update the spec instead of the browsers. Do you have a spec issue where browser vendors indicate they agree to update the behaviour? If not, I don't think we should update the test and instead match their behaviour and update the spec.

No. The test is written 6 years ago and spec got updated. The upstream is being reviewed, and bug is confirmed in bugzilla link above.

Such things happen several times before, where the spec is ahead of vendors: e.g. window rect.

@TimvdLippe
Copy link
Copy Markdown
Contributor

I can't find the link to the spec change. The Bugzilla link is for Firefox only. Can you provide the link to the commit/PR that changed the spec?

@yezhizhen
Copy link
Copy Markdown
Member Author

@TimvdLippe Thanks for taking a look. I found it to be here: w3c/webdriver#1802.

The review's been delegated to web-platform-tests/wpt#56959, similar to #39988 before.

Copy link
Copy Markdown
Contributor

@TimvdLippe TimvdLippe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good! I approve this PR, but please don't merge until you have full approval on web-platform-tests/wpt#56959

@servo-highfive servo-highfive removed the S-awaiting-review There is new code that needs to be reviewed. label Jan 4, 2026
@yezhizhen
Copy link
Copy Markdown
Member Author

Sounds good! I approve this PR, but please don't merge until you have full approval on web-platform-tests/wpt#56959

Definitely!

@servo-highfive servo-highfive added the S-awaiting-review There is new code that needs to be reviewed. label Jan 5, 2026
@servo-wpt-sync
Copy link
Copy Markdown
Collaborator

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#56959).

@yezhizhen yezhizhen added this pull request to the merge queue Jan 5, 2026
@servo-highfive servo-highfive added the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Jan 5, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 5, 2026
@servo-highfive servo-highfive added S-tests-failed The changes caused existing tests to fail. and removed S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. labels Jan 5, 2026
WebDriverError::new(ErrorStatus::InvalidArgument, "Invalid value for {key}")
})? as u64),
Value::Number(num) => Some(
num.as_u64()
Copy link
Copy Markdown
Member Author

@yezhizhen yezhizhen Jan 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad. It panicked with 2.0, which is valid according to spec.

Signed-off-by: Euclid Ye <[email protected]>
Signed-off-by: Euclid Ye <[email protected]>
@servo-highfive servo-highfive removed the S-tests-failed The changes caused existing tests to fail. label Jan 5, 2026
@yezhizhen yezhizhen enabled auto-merge January 5, 2026 11:06
@yezhizhen yezhizhen disabled auto-merge January 5, 2026 11:07
@servo-wpt-sync
Copy link
Copy Markdown
Collaborator

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#56959).

@yezhizhen yezhizhen added the T-webdriver Do a try run of the WebDriver conformance tests label Jan 5, 2026
@github-actions github-actions bot removed the T-webdriver Do a try run of the WebDriver conformance tests label Jan 5, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 5, 2026

🔨 Triggering try run (#20713924804) for Linux (WPT)

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 5, 2026

Test results for linux-wpt from try job (#20713924804):

Flaky unexpected result (1)
  • OK /webdriver/tests/classic/perform_actions/wheel.py
    • ERROR [expected PASS] subtest: test_null_response_value

      teardown error: 
      

    • ERROR [expected PASS] subtest: test_no_top_browsing_context

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_no_browsing_context

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_params_actions_origin_outside_viewport[element]

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_params_actions_origin_outside_viewport[viewport]

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_scroll_not_scrollable

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_scroll_scrollable_overflow

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_scroll_iframe

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_scroll_shadow_tree[outer-open]

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • ERROR [expected PASS] subtest: test_scroll_shadow_tree[outer-closed]

      setup error: ConnectionRefusedError: [Errno 111] Connection refused
      

    • And 3 more unexpected results...

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 5, 2026

✨ Try run (#20713924804) succeeded.

@yezhizhen yezhizhen added this pull request to the merge queue Jan 5, 2026
@servo-highfive servo-highfive added the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Jan 5, 2026
Merged via the queue into servo:main with commit 0022d97 Jan 5, 2026
47 checks passed
@yezhizhen yezhizhen deleted the go branch January 5, 2026 12:29
@servo-highfive servo-highfive removed the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Jan 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-awaiting-review There is new code that needs to be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants