Bug 1821807 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Here's a testcase with just `linear-gradient` (no image-set).

We support linear-gradient as a value for `background-image` but not for `content` apparently.
Chrome does support it as a value for `content` (renders a lime rect).
Epiphany/WebKit sort-of supports it -- they render a transparent black-bordered div in this testcase, for some reason.  I think that indicates that they're parsing it successfully but they're failing to paint it for some reason.
Here's a testcase with just `linear-gradient` (no image-set), for simpler cross-browser comparisons, since not all browsers support `image-set`.

We support linear-gradient as a value for `background-image` but not for `content` apparently.
Chrome does support it as a value for `content` (renders a lime rect).
Epiphany/WebKit sort-of supports it -- they render a transparent black-bordered div in this testcase, for some reason.  I think that indicates that they're parsing it successfully but they're failing to paint it for some reason.
Here's a testcase with just `linear-gradient` (not `image-set`) in the content property, for simpler cross-browser comparisons, since not all browsers support `image-set`.

We support linear-gradient as a value for `background-image` but not for `content` apparently.
Chrome does support it as a value for `content` (renders a lime rect).
Epiphany/WebKit sort-of supports it -- they render a transparent black-bordered div in this testcase, for some reason.  I think that indicates that they're parsing it successfully but they're failing to paint it for some reason.

Back to Bug 1821807 Comment 1