-
Notifications
You must be signed in to change notification settings - Fork 715
[css-images-4] Allow gradient color stops to have two locations #2439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
The Working Group just discussed
The full IRC log of that discussion<dael> Topic: Clear gradient color stops with two locations for shipping<ChrisL> q+ to a) express support for dry two-location stops and b) ask whether chrome does computed-value-time fixup or post-layout fixup <dael> github: https://github.com//issues/2439 <dael> leaverou: Two weeks ago we cleared conic gradient for shipping. Turns out many conic gradient in the wild were using the two locatiosn. It's been in the draft for 6 years. Chrome impl a year ago because it was in many demos <dael> leaverou: Dev that impl asked if he can ship it as well. Chrome impl a year ago. I don't see why not. <dael> ChrisL: I think it's an obvious good thing. <dael> leaverou: It's what I said in issue. <dael> ChrisL: Question for chrome folks. THere's a question in the spec as to if fixup applies before or after layout. I don't think that effects this issue. <dael> leaverou: I don't see why depend on layout <dael> ChrisL: There's an issue that says it might <fantasai> I thought we resolved on that in Tokyo? <dael> TabAtkins: Not sure <dael> ChrisL: Can you find out? <dael> ChrisL: IN general I support this. <AmeliaBR> +1, this is a very useful syntax (especially when using variables in gradients), doesn't involve any new rendering code, only computed value changes. <dael> ChrisL: People are using it and it's a trvial extension. <dael> Rossen_: Hearing some support. Other opinions? Esp from Chrome folks who are shipping? <dael> TabAtkins: I'm fine with shipping I agree it's minor feature very useful. <tantek> we have tests? <fantasai> ChrisL, https://lists.w3.org/Archives/Public/www-style/2017May/0051.html <leaverou> tantek: we don't have test for ANYTHING about gradients! <leaverou> s/test/tests/ <tantek> SMH <dael> Rossen_: Objections to color stops are extended into their consecutive color stops? <dael> leaverou: Color stops with two positions <tantek> so now we're agreeing to ship features based on demoware? <AmeliaBR> It's basically adopt https://drafts.csswg.org/css-images-4/#color-stop-syntax <leaverou> Color stops with two positions are expanded to two consecutive color stops with the same color <dael> frremy: This is in spec we just have to say fine to ship <dael> leaverou: Yes. <dael> Rossen_: I heard no objections. <dael> RESOLVED: clear gradient color stops with two locations for shipping <tantek> just WD right? |
Please don't use "clear" in the context of colors unless you are referring to "the clear color" |
"The clear color" isn't even a term of art! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
Last week we cleared
conic-gradient()
for shipping.It turns out that many conic gradient demos are also using the two position color stop syntax, since the
conic-gradient()
polyfill supported that too, so the Chrome developer implemented that as well. He asked me today if this has to wait until CR or it can be shipped alongside conic-gradient().The feature is that gradient color stops can have two positions, and they are expanded into two consecutive color stops with the same color, which is useful for creating "bands" of color.
My arguments for clearing this too:
The text was updated successfully, but these errors were encountered: