You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One solution would be to search for alternatives of the 'problem-causing properties' (like using box-shadow instead of filter: drop-shadow). I would however prevent the problem by only allow using fixed for 'top-layer' components. Similar to how we work with portals.
There are probably multiple solutions to this, portals would be one, but that might be obsolete with <dialog and the concept of top layer. If this problem exists in the top layer as well I don't know, we would have to research this.
The text was updated successfully, but these errors were encountered:
There is also a good chance that using the transform, filter, or will-change: transform do not make sense in ancestors and should be prevented there so that they only apply to leaf nodes.
I don't think this can be done with stylelint alone.
The problem: when you define
transform
,filter
, orwill-change
, any child withposition: fixed
will no longer be fixed (https://meyerweb.com/eric/thoughts/2011/09/12/un-fixing-fixed-elements-with-css-transforms/).One solution would be to search for alternatives of the 'problem-causing properties' (like using
box-shadow
instead offilter: drop-shadow
). I would however prevent the problem by only allow using fixed for 'top-layer' components. Similar to how we work with portals.There are probably multiple solutions to this, portals would be one, but that might be obsolete with
<dialog
and the concept of top layer. If this problem exists in the top layer as well I don't know, we would have to research this.The text was updated successfully, but these errors were encountered: