Join GitHub today
[css-images-4] Clear conic-gradient() for shipping #2383
Chrome implemented conic-gradient() last year behind a flag and now wants to ship. Some internal teams have expressed interest in using conic-gradient on consumer products, and they would rather see the feature shipped than provide back-doors.
I checked and there are no open issues about conic-gradient here. Chrome's implementation has also been tested a fair bit by authors creating demos and beyond a few rendering quality issues with the GPU backend, there are no outstanding problems.
Spec-wise, conic-gradient has been in some Images draft for five years or so.
I think it makes sense to clear this for shipping, and is certainly better than the alternative.
Adding this to the agenda so we can discuss this Wednesday.
referenced this issue
Mar 5, 2018
The Working Group just discussed
The full IRC log of that discussion<dael> Topic: [css-images-4] Clear conic-gradient() for shipping
<fantasai> ping leaverou_
<dael> github: https://github.com//issues/2383
<dael> astearns: leaverou_ put it in the issue
<dael> astearns: There's an impl, there's not outstanding problems. She things it'stime to clear it for shipping as Chrome wants to ship. Likely won't be problems when other engines impl.
<dael> Chris: I agree. The polyfill has been out for a while and the syntax is stable.
<dael> florian: No problem
<dael> leaverou_: Impl has been out for a year as well
<leaverou_> The implementatuon has been our for a year too
<florian> I support clearing it for shipping
<dael> astearns: Any concerns about clearing for shipping?
<dael> astearns: Obj for clearing conic-gradient for shipping?
<dael> RESOLVED: Clear conic-gradient() for shipping
<RRSAgent> I have made the request to generate https://www.w3.org/2018/03/07-css-minutes.html Chris
Chrome Intent to Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ySuNvyaB8jY