135243 2014-07-24 11:25:32 -0700 Pseudo-elements should not display a resize handle when styled with the css3-ui `resize` property 2024-10-24 06:27:51 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) Mac (Intel) OS X 10.9 RESOLVED DUPLICATE 267519 http://result.dabblet.com/gist/ab432c3f6a8f672cd077 InRadar, WPTImpact P2 Normal --- 1 lea webkit-unassigned ahmad.saleem792 bfulgham dholbert simon.fraser webkit-bug-importer oldest_to_newest 1024533 0 lea 2014-07-24 11:25:32 -0700 Although a resize handle is shown, the pink pseudo-element in the testcase above cannot actually be resized. css3-ui states that the resize property applies to “elements with ‘overflow’ other than visible”, which includes pseudo-elements. 1211613 1 dholbert 2016-07-15 15:39:12 -0700 (In reply to comment #0) > css3-ui states that the resize property applies to “elements with ‘overflow’ > other than visible”, which includes pseudo-elements. The css3-ui spec now also says "Implementations should not apply the resize property to generated content." That includes the pseudo-element in the dabblet testcase here. Spec link: http://dev.w3.org/csswg/css-ui/#resize So, I think the (current) expected behavior here is that WebKit shouldn't be showing a resizer on that pseudo-element. (The resize property "should not apply", i.e. it shouldn't affect rendering at all.) Incidentally, Firefox/Gecko recently changed to have that behavior (not showing a resizer) in https://bugzilla.mozilla.org/show_bug.cgi?id=1043537 1883492 2 bfulgham 2022-07-13 17:25:04 -0700 Safari continues to show a resize handle, when it should not. 1883493 3 webkit-bug-importer 2022-07-13 17:25:19 -0700 <rdar://problem/96983000> 1990374 4 ahmad.saleem792 2023-11-06 17:33:08 -0800 https://wpt.fyi/results/css/css-ui/resize-generated-content.html?label=master&label=experimental&aligned&q=safari%3Afail Live Link: http://wpt.live/css/css-ui/resize-generated-content.html 2070348 5 ahmad.saleem792 2024-10-24 06:27:51 -0700 Progressed with 285644@main *** This bug has been marked as a duplicate of bug 267519 ***