Bug 135243
| Summary: | Pseudo-elements should not display a resize handle when styled with the css3-ui `resize` property | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Lea Verou <lea> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ahmad.saleem792, bfulgham, dholbert, simon.fraser, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar, WPTImpact |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac (Intel) | ||
| OS: | OS X 10.9 | ||
| URL: | http://result.dabblet.com/gist/ab432c3f6a8f672cd077 | ||
Lea Verou
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Daniel Holbert
(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
Brent Fulgham
Safari continues to show a resize handle, when it should not.
Radar WebKit Bug Importer
<rdar://problem/96983000>
Ahmad Saleem
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
Ahmad Saleem
Progressed with 285644@main
*** This bug has been marked as a duplicate of bug 267519 ***