Custom Component 2.0 breaking sticky global headers

Hello!

I’m encountering an issue where the use of any custom component made with the 2.0 system is now causing sticky headers to have broken width/height settings. This seems to happen because a tailwind.css file is being injected in the head of the main app and picking up the ‘.fixed’ class on the element of the global header.

Also, the tailwind.css inclusion happens regardless of what is actually in the custom component packages.json. It seems to be an inherent part of adding any custom component made with 2.0 to any page in an app.

There are other issues to related to this, but that was the one that caught my attention initially and have the most context on.

Let me know if you need more info - this is causing a lot of issues on our end.

Thanks!

Hi @Audio

Sorry about that!

Would you mind sending me a video of this happening, as well as an export of the affected app, if it’s possible? Please use my email address kate@uibakery.io.

Thank you!

Sent - thanks again!

Thank you, I’ve received it