- From: Karl Dubost via GitHub <noreply@w3.org>
- Date: Tue, 20 Jan 2026 06:44:30 +0000
- To: public-svg-issues@w3.org
@Ahmad-S792 Sorry, I had misunderstood. I thought browsers were doing what the spec was saying for Firefox and Chrome and it seems they do not. My interpretation of the spec. is that 1. if `fx` is defined, the value doesn't change 2. if `fx` is not defined/invalid **and** `cx` is defined, `fx` takes the value of `cx` 3. if `fx` is not defined/invalid **and** `cx` is not defined or invalid, `cx` takes the value `50%` **and** `fx` inherits this value which is `50%` And if what it is the what the spec mandates then no browsers is following the spec, and we need to modify the spec to the path of least resistance. Here the text with my assumptions which scenario not tested on WPT. [gradient-test.html](https://github.com/user-attachments/files/24730583/gradient-test.html) -- GitHub Notification of comment by karlcow Please view or discuss this issue at https://github.com/w3c/svgwg/issues/1054#issuecomment-3771284798 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 January 2026 06:44:31 UTC