Closed AlexDaniel closed 1 year ago
Hi @AlexDaniel! 👋
It looks like you provided an invalid or unsupported reproduction URL. Do not use any service other than Codepen, jsFiddle, StackBlitz, Codesandbox, and GitHub. Make sure the URL you provided is correct and reachable. You can test it by visiting it in a private tab, another device, etc. Please edit your original post above and provide a valid reproduction URL as explained.
Without a proper reproduction, your issue will have to get closed.
Thank you for your collaboration. 👏
Hi,
Thanks for bringing this up. Will be fixed in the next release.
What happened?
When combining Quasar with BabylonJS, normalize.sass styles are breaking the Node Material Editor in BabylonJS.
What did you expect to happen?
Quasar's css corrections should be neutral for most other libraries.
Reproduction URL
.
How to reproduce?
Actually, easier said than done… It's pretty straightforward but takes some time. Given that the fix is already in normalize.css, please let me know if I should actually provide something for reproducing this.
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Style & Identity (quasar)
Platforms/Browsers
Firefox, Chrome
Quasar info output
No response
Relevant log output
No response
Additional context
Please see this ticket:
What happens is that BabylonJS is using an
<svg>
element that is arbitrarily sized, and then it expects the rendered elements to overflow.However,
quasar
sets this style:Which seems to change the default expectation. Therefore, content gets clipped.
This issue has been raised in normalize.css:
And it was resolved by this commit:
However, that change was not ported to Quasar yet. I think it should be.