Bug 29824
Summary: | <video> element is not clipped with -webkit-border-radius | ||
---|---|---|---|
Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | eric.carlson, hyatt, miketaylr, simon.fraser, webkit |
Priority: | P2 | Keywords: | InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 36642 | ||
Bug Blocks: |
David Kilzer (:ddkilzer)
* SUMMARY
The <video> element (which is displaying an image) in LayoutTests/fast/replaced/border-radius-clip.html is not clipped by the -webkit-border-radius CSS applied to the element.
* STEPS TO REPRODUCE
1. Launch Safari or a WebKit nightly build.
2. Open: LayoutTests/fast/replaced/border-radius-clip.html
* RESULTS
The <video> element is not clipped.
* REGRESSION
I assume the layout test was working when it was checked in.
* NOTES
See Bug 21789 for the original fix.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
(In reply to comment #0)
> * REGRESSION
> I assume the layout test was working when it was checked in.
Not a regression as the <video> element was never clipped in r41952 either.
Simon Fraser (smfr)
Probably regressed when we enabled hardware video.
Simon Fraser (smfr)
<rdar://problem/7797572>
Mike Taylor
A bug was filed at webcompat.com related to this, but for unprefixed border-radius (which probably doesn't matter in practice):
https://github.com/webcompat/web-bugs/issues/12357
codepen here:
https://codepen.io/hetgelaat/pen/dVjZWE
Eric Carlson
(In reply to Mike Taylor from comment #4)
> A bug was filed at webcompat.com related to this, but for unprefixed
> border-radius (which probably doesn't matter in practice):
>
> https://github.com/webcompat/web-bugs/issues/12357
>
> codepen here:
>
> https://codepen.io/hetgelaat/pen/dVjZWE
The webcompat.com is about Chrome, which doesn't use WebKit. The codepen works in the current version of Safari, so marking this bug as closed.