Skip to content

Fix description of computing pointer-interactable paint tree#1927

Merged
whimboo merged 3 commits into
w3c:masterfrom
yezhizhen:fix-in-view
May 11, 2026
Merged

Fix description of computing pointer-interactable paint tree#1927
whimboo merged 3 commits into
w3c:masterfrom
yezhizhen:fix-in-view

Conversation

@yezhizhen
Copy link
Copy Markdown
Member

@yezhizhen yezhizhen commented Sep 11, 2025

The step of in-view center point already computes the first object of getClientRects on element. This PR makes the description more accurate.


Preview | Diff

@yezhizhen
Copy link
Copy Markdown
Member Author

cc @xiaochengh

@yezhizhen yezhizhen marked this pull request as ready for review September 11, 2025 09:50
@yezhizhen
Copy link
Copy Markdown
Member Author

@whimboo Can you help check this small one too?

Copy link
Copy Markdown
Contributor

@whimboo whimboo left a comment

Choose a reason for hiding this comment

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

Thanks for the fixes. That was indeed broken. Maybe you can take a look at the inline comment?

Comment thread index.html Outdated

<ol>
<li><p>If <var>element</var> is <a>not in the same tree</a>
<li><p>If <a><var>element</var></a> is <a>not in the same tree</a>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think that this is correct, bu in other places we use <var><a> so we should be consistent.

But I wonder if we always want to link the element. There are a lot of other instances where we don't do that. So maybe a separate PR fixing all the cases might be good if we wanna have that? But that's not blocking landing this PR.

Copy link
Copy Markdown
Member Author

@yezhizhen yezhizhen May 7, 2026

Choose a reason for hiding this comment

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

That's a good point. Sometimes we call "element element", https://w3c.github.io/webdriver/#dfn-disabled
where the first element links to the Element interface.

For this one, I will just remove the link.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I have refactored this same way as how we deal with disabled.

yezhizhen added 2 commits May 7, 2026 16:50
Signed-off-by: Euclid Ye <euclid.ye@huawei.com>
Signed-off-by: Euclid Ye <euclid.ye@huawei.com>
Signed-off-by: Euclid Ye <euclid.ye@huawei.com>
@yezhizhen yezhizhen requested a review from whimboo May 7, 2026 09:02
Copy link
Copy Markdown
Contributor

@whimboo whimboo left a comment

Choose a reason for hiding this comment

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

This looks good now and matches what we have for An element element is disabled.

Thanks!

@whimboo whimboo merged commit 6bd15e4 into w3c:master May 11, 2026
2 checks passed
github-actions Bot added a commit that referenced this pull request May 11, 2026
SHA: 6bd15e4
Reason: push, by whimboo

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@yezhizhen yezhizhen deleted the fix-in-view branch May 11, 2026 11:39
github-actions Bot added a commit to soloinovator/webdriver that referenced this pull request May 11, 2026
SHA: 6bd15e4
Reason: push, by pull[bot]

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions Bot added a commit to xjc90s/webdriver that referenced this pull request May 11, 2026
SHA: 6bd15e4
Reason: push, by pull[bot]

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants