Bug 243853 - REGRESSION (STP 151): Neowin.net website theme toggle is misaligned
Summary: REGRESSION (STP 151): Neowin.net website theme toggle is misaligned
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: Safari 15
Hardware: Mac (Apple Silicon) macOS 12
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-08-11 15:56 PDT by Ahmad Saleem
Modified: 2022-08-29 07:37 PDT (History)
8 users (show)

See Also:

Attachments
Safari 15.6 vs STP 151 (196.04 KB, image/png)
2022-08-11 15:59 PDT, Ahmad Saleem 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmad Saleem 2022-08-11 15:56:46 PDT 
Hi Team,

Just after the release of STP 151 few minutes ago, I noticed that the www.neowin.net website has misaligned theme button as below (please refer to attached screenshot).

Link - https://www.neowin.net

EXPECTED RESULT - It should render same as Safari 15.6

I don't have any reduction or test case but I will look into it but wanted to raise it as soon as possible.

Further, the spacing is also broken on WPT website: https://wpt.fyi/results/svg/idlharness.window.html?label=experimental&label=master&aligned&view=subtest

I have raised these in #webkit Slack #help channel as well.

Looking forward for your support. Thanks!
Comment 1 Ahmad Saleem 2022-08-11 15:59:22 PDT 
Created attachment 461549 [details]
Safari 15.6 vs STP 151
Comment 2 Simon Fraser (smfr) 2022-08-11 16:11:38 PDT 
Misplaced item has `display: inline-block; vertical-align:baseline`;
Comment 3 Radar WebKit Bug Importer 2022-08-11 16:12:30 PDT 
<rdar://problem/98535282>
Comment 4 Ahmad Saleem 2022-08-29 06:40:32 PDT 
This is also not reproducible in STP 152 and I don't know which commit fixed it. If anyone can point else I can close this as "RESOLVED CONFIGURATION CHANGED"? Thanks!
Comment 5 zalan 2022-08-29 06:42:11 PDT 
(In reply to Ahmad Saleem from comment #4)
> This is also not reproducible in STP 152 and I don't know which commit fixed
> it. If anyone can point else I can close this as "RESOLVED CONFIGURATION
> CHANGED"? Thanks!
Looking