cmahnke

@simonheimlicher Thanks for those suggestions, in my "kitchen sink"-theme I already do that partly (currently missing the `page.RelPermalink` part). What you are actually are doing is to use the buildin...

To have a symmetric user interface, many `docker` commands support a `--force` switch.

Please reopen, this is still desirable. From what I understand the issue itself is about the general functionality, the reason why this was closed relates to the usage on Mermaid...

@vincentfretin: Thanks, my "frame" uses, or better: used until now (global) `static`, `content` and a few more from the above, where `content` had the most visible (making the inspector nearly...

@dmarcos: Issues also arise when the surrouding website (or CMS theme or whatever) provides a global `.content` stylesheet... There's also the option of running A-Frame inside an iframe to prevent...

@dmarcos: From what I've read about the possible options, which are: * Prefixing (Requires changes in React code as well) * Using React CSS Modules (provided for example by [`styled-components`](https://styled-components.com/)...

Thanks for the clarification @vincentfretin I wasn't aware of this distinction / possibility. Then as you propose.

@dmarcos: Well, it was my understanding that this is a change which is required on the inspector side...

My consideration was that the code is actually already there, but it's not fleshed out yet: A extremely low hanging fruit. Since I already tried the combination `xr-mode-ui="enabled: true; enterVREnabled:...

Well, what I meant is just that I wanted to disable potentially / confusing (as in getting unwanted bug reports) misleading functionality. Thanks for the hint, I'll try that one...