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
Currently Manon explicitly targets some elements as direct descendants of body, for example body > main and body > header nav.collapsible. This makes it impossible to use Manon correctly in contexts where a page-wide wrapping element is required, for example when using a frontend framework that might otherwise interfere with elements that are appended to the body by browser extensions.
For some components, an undocumented alternative way to target it is supported, such as the .page-header and .page-footer classes.
It would be nice if this could be supported (and documented) for all cases. Or perhaps a simpler approach could be adopted (if possible): adding a .manon-root class that can act as a stand-in for body in these cases:
Currently Manon explicitly targets some elements as direct descendants of
body
, for examplebody > main
andbody > header nav.collapsible
. This makes it impossible to use Manon correctly in contexts where a page-wide wrapping element is required, for example when using a frontend framework that might otherwise interfere with elements that are appended to thebody
by browser extensions.For some components, an undocumented alternative way to target it is supported, such as the
.page-header
and.page-footer
classes.It would be nice if this could be supported (and documented) for all cases. Or perhaps a simpler approach could be adopted (if possible): adding a
.manon-root
class that can act as a stand-in forbody
in these cases:The text was updated successfully, but these errors were encountered: