Removed here: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-May/011335.html>. Gecko also supports "clear" and "over" (synonym of "source-over").

Ref <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-April/010735.html> <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-June/012063.html>

Ok thank you for the info.

I'd still like it specified, though. The lack of interoperability now isn't a reason not to improve the situation.

Given the (at least) three different behaviours that have been implemented for "darker" (http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-March/010608.html), what behaviour do you want to be specified?

(In reply to comment #4)
> Given the (at least) three different behaviours that have been implemented for
> "darker"
> (http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-March/010608.html),
> what behaviour do you want to be specified?

Any, if it's implementable across platforms. I'd be fine with dropping support in browsers, but as that hasn't happened since you proposed to drop it 3 years ago, it doesn't look like that will happen.

I guess the question is whether they've kept support because they need to maintain compatibility with content (though presumably the content's compatibility requirements aren't too strict given that the browsers all handle it differently today), in which case the spec should spec it, or whether it's because they don't care about it and it's a very low priority to spend any effort on, in which case it will be easier to achieve interoperability by having them remove the feature than by having them spend much more effort implementing a specific behaviour for it.

Perhaps. I filed a bug on Mozilla: <https://bugzilla.mozilla.org/show_bug.cgi?id=571532>.

And fixed it.

And filed a bug on WebKit as well: <https://bugs.webkit.org/show_bug.cgi?id=43739>.