113839 2013-04-02 17:33:58 -0700 Display: switching from display:block to display: table-cell getting confused on window resize when using media queries 2022-06-09 11:38:20 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 138167 http://jsbin.com/iliniw/1/edit P2 Normal --- 0 msnazi webkit-unassigned ahmad.saleem792 ap koivisto rniwa webkit zalan oldest_to_newest 868367 0 msnazi 2013-04-02 17:33:58 -0700 Chrome Version : 27.0.1454.0 (Official Build 190834) canary URLs (if applicable) : http://jsbin.com/iliniw/1/edit Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: FAIL Firefox 4.x: OK IE 7/8/9: only tested in IE8: FAIL Safari 6: FAIL What steps will reproduce the problem? 1. Go to this URL: http://jsbin.com/iliniw/1/edit 2. Resize the preview window to make it narrow (less than 500px) 3. Resize the preview window to make it wide (more than 500px) What is the expected result? columns should show up next to each other with similar width What happens instead? first column is wider and other two columns are smaller Please provide any additional information below. Attach a screenshot if possible. Seems like it's a webkit bug. I've filed a similar bug in bug in Chromium project. https://code.google.com/p/chromium/issues/detail?id=225946 1166358 1 webkit 2016-02-18 23:50:10 -0800 Presumably a duplicate of bug 138167. 1875026 2 ahmad.saleem792 2022-06-09 09:36:16 -0700 I am unable to reproduce following bug using URL (JS Bin) in Safari 15.5 on macOS 12.4. Across all other browsers, Chrome Canary 104 and Firefox Nightly 103, it works same. Columns show up when resizing with enough width and disappear when making view window smaller. All spaced tables look same across browsers. If I am testing incorrectly, please retest accordingly. Although I think this was fixed within Webkit along the lines and now can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks! 1875059 3 ap 2022-06-09 11:38:20 -0700 Duping as suggested. *** This bug has been marked as a duplicate of bug 138167 ***