- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Sep 2018 17:02:17 +0000
- To: public-fxtf-archive@w3.org
> I used white for two reasons: > > 1. The de facto state of browsers is that they use a white background > 2. To make the explainer easier to read, so white is also a placeholder I don't think saying that it composites against opaque white is any simpler than saying it just does against "the backdrop", with a definition that the backdrop is whatever the UA wants it to be (typically transparent for iframes and opaque white for root-level documents, but can be anything). Given that all you're doing with it is compositing over it, the identity of it doesn't matter, and being unnecessarily specific makes it *harder* to read when you actually know the details. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/282#issuecomment-420723346 using your GitHub account
Received on Wednesday, 12 September 2018 17:02:18 UTC