- From: Matthew Dean via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Feb 2018 18:28:12 +0000
- To: public-css-archive@w3.org
> Is this issue removing transform as a containing block for fixed-position elements? I don't think that is a good idea, as it: > makes clipping and filter effects hard to define and implement, and in general ill-defined because > it's impossible to "filter" across multiple 2d planes. > introduces difficult and complex code to implement compositing > makes it hard to provide clean fast paths for transforms None of the "implementation is really difficult" seems relevant in terms of what makes sense in consistency of the language. `position: fixed` should always maintain that element in relation to the viewport. Setting a transform should not make it "steal" a fixed-positioned element from the viewport and inject it into its own context as if it's `position: absolute`. Algorithmically, you should still be able to scale/translate/rotate a fixed-positioned element based on it's original "viewport" position without changing what its height/width/top/left values initially mean. -- GitHub Notification of comment by matthew-dean Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/913#issuecomment-369335453 using your GitHub account
Received on Wednesday, 28 February 2018 18:28:13 UTC