REOPENED306818
Incorrect outlineWidth in result of getComputedStyle when OutlineStyle is None 
https://bugs.webkit.org/show_bug.cgi?id=306818
Summary Incorrect outlineWidth in result of getComputedStyle when OutlineStyle is None
mechannik512
Reported 2026-02-02 16:41:11 PST
If OutlineStyle is None, getComputedStyle should return outlineWidth equal to 0, but now it returns 3
Attachments
Add attachment proposed patch, testcase, etc.
mechannik512
Comment 1 2026-02-02 16:55:18 PST
Pull request: https://github.com/WebKit/WebKit/pull/57740
Sam Weinig
Comment 2 2026-02-02 18:54:36 PST
As mentioned in the PR, the current behavior is correct as of CSS UI 4, due to the CSSWG resolution https://github.com/w3c/csswg-drafts/issues/11494. Is this change in behavior causing an issue for you?
mechannik512
Comment 3 2026-02-03 00:17:30 PST
> Is this change in behavior causing an issue for you? Yes it does (custom JS code of making element screenshot on page, when calculating element coords, includes element outline width, which just changed for all elements) But since it aligns with CSS UI 4, its not a bug.
mechannik512
Comment 4 2026-02-03 04:54:58 PST
Wait, shouldn't we still return "0px" when outline is "none" for compatibility reasons, as described here? https://github.com/w3c/csswg-drafts/issues/11494#issuecomment-2675800489
Sam Weinig
Comment 5 2026-02-04 09:20:32 PST
Perhaps, re-opening this while we take this up with the working group. I filed https://github.com/w3c/csswg-drafts/issues/13451 to start that discussion.
Sam Weinig
Comment 6 2026-02-04 09:22:12 PST
mechannik512, are you able to provide a link to the content where this bug is hitting, or is this something that is private?
mechannik512
Comment 7 2026-02-04 09:27:07 PST
(In reply to Sam Weinig from comment #6) > mechannik512, are you able to provide a link to the content where this bug > is hitting, or is this something that is private? Not private. Its piece of code where we calculate coords of an element so we could extract that area from viewport screenshot. Here is link to PR where i fix it on the side of our tool: https://github.com/gemini-testing/testplane/pull/1198/changes
Note You need to log in before you can comment on or make changes to this bug.