Bug 183121 - Page using grid layout is different between Safari and Chrome
Summary: Page using grid layout is different between Safari and Chrome
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: Safari 11
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-26 03:51 PST by Tobi Reif
Modified: 2018-02-27 13:32 PST (History)
3 users (show)

See Also:


Attachments
screenshot_safari.png (534.53 KB, image/png)
2018-02-26 03:51 PST, Tobi Reif
no flags Details
screenshot_chrome.png (374.33 KB, image/png)
2018-02-26 03:52 PST, Tobi Reif
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tobi Reif 2018-02-26 03:51:40 PST
Created attachment 334605 [details]
screenshot_safari.png

(Please set the right component.)
(Please set the right title/summary.)

When I open this page https://tobireif.com/demos/grid/ in Safari in a 583px wide window (sized eg by overlaying it onto a Chrome window of that width), I get the rendering shown in screenshot_safari.png , which is different from Chrome's rendering shown in screenshot_chrome.png .
Comment 1 Tobi Reif 2018-02-26 03:52:11 PST
Created attachment 334606 [details]
screenshot_chrome.png
Comment 2 Tobi Reif 2018-02-26 03:53:47 PST
Unfortunately I don't have the chance to find the time to investigate this more, but I thought I'd let you know about it so that you can fix it if you want.
Comment 3 Tobi Reif 2018-02-27 13:28:13 PST
I can't reproduce this anymore, please close.

(I hadn't attached a snapshot zip, sorry.)

Perhaps it was related to the bug where test-strokes are rendered with half the width in WebKit -> less total text width -> different trigger dimensions for element queries.
Comment 4 Tobi Reif 2018-02-27 13:29:50 PST
This must be the worst bug report ever. I'll try to do better in the future 😀
Comment 5 zalan 2018-02-27 13:32:02 PST
(In reply to Tobi Reif from comment #4)
> This must be the worst bug report ever. I'll try to do better in the future
> 😀
:) 
>I can't reproduce this anymore, please close.
You can also close the bug by changing the status to Resolved/worksforme.