Bug 203589 - Wikipedia sidebar is always cut off by edge of window
Summary: Wikipedia sidebar is always cut off by edge of window
Status: RESOLVED DUPLICATE of bug 115156
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: zalan
URL: https://en.wikipedia.org/wiki/Normal_...
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2019-10-29 14:41 PDT by Myles C. Maxfield
Modified: 2020-05-20 02:41 PDT (History)
5 users (show)

See Also:


Attachments
Screenshot (490.64 KB, image/png)
2019-10-29 14:41 PDT, Myles C. Maxfield
no flags Details
A simplified tets-case (286 bytes, text/html)
2020-05-19 23:34 PDT, Noam Rosenthal
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Myles C. Maxfield 2019-10-29 14:41:16 PDT
Created attachment 382228 [details]
Screenshot

See right edge of attached screenshot. Even if you resize the window, the sidebar is always cut off.
Comment 1 Radar WebKit Bug Importer 2019-10-29 14:41:57 PDT
<rdar://problem/56721998>
Comment 2 Myles C. Maxfield 2019-10-29 14:42:44 PDT
It's not cut off in Chrome or Firefox.
Comment 3 zalan 2019-10-29 14:46:22 PDT
There's something wrong with computing the table preferred width and we end up layout overflowing it.
removing the max-width property from the table fixes the sizing and the page is no longer scrollable horizontally. :(
Comment 4 Noam Rosenthal 2020-05-19 23:34:17 PDT
Created attachment 399817 [details]
A simplified tets-case

From this test case, it seems that WebKit treats table layouts as "fixed" by default while other browsers don't. Maybe there's another bug open for this
Comment 5 Noam Rosenthal 2020-05-20 01:37:25 PDT
I'm pretty sure this is the same as https://bugs.webkit.org/show_bug.cgi?id=109462
Comment 6 Noam Rosenthal 2020-05-20 02:41:46 PDT
This is about max-width not being properly applied. This already has an open bug from 2013.

*** This bug has been marked as a duplicate of bug 115156 ***