- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Apr 2018 10:25:38 +0000
- To: public-css-archive@w3.org
In all honesty, better terminology needs to be created for how a `fixed` positioned elements containing block is defined, beyond just `transform`... - Firefox and blink are also affected by `perspective` not set to `none`, which makes sense in line with `transform`. - Firefox is affected by `filter` not set to `none`, making a leap from just informing the stacking context or isolation. - Safari (desktop) only uses `transform` not set to `none`, yet `perspective` not set to `none` will still create a stacking context and there is no mention of this in the spec. - Not as intimate with or sure of how Edge relates to this? I understand that moving relationships of elements around different representations of the tree isn't easy and this issue isn't about removing `transform` affecting `fixed` (has anyone else seen iOS Safari juttering `fixed` elements when they are nested inside `-webkit-overflow-scrolling: touch`?), but there are serious compatibility issues that should be ironed out or at least... ...documented within [css-position](https://drafts.csswg.org/css-position-3/#fixed-pos). -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/913#issuecomment-381093941 using your GitHub account
Received on Friday, 13 April 2018 10:25:42 UTC