Chris Simmons
Chris Simmons
@Haiz14 @Xenon27 I was able to replicate a similar issue last week when testing Skeleton for a Next.js project with Turbopack enabled. Can the two of you confirm which framework...
Just FYI folks, we've made some headway on this. We have a PR pending. We'll test and release a patch asap: - https://github.com/skeletonlabs/skeleton/pull/2931
@Haiz14 @Xenon27 @slythom we've just pushed out an update to the core package. That should be: ``` @skeletonlabs/skeleton 3.0.0-next.7 ``` If you guys would please update and verify this resolves...
Glad to hear! We'll await confirmation from a couple other folks before we close out the issue.
We've had a number of folks confirm this fix on Discord, so I'm going go ahead and close this out. Thanks!
See also: https://github.com/skeletonlabs/skeleton/issues/2964#issuecomment-2707688441
Thank you for reporting, we'll aim to review asap!
@laszlo1337 sorry it's taken us a bit to get back to this. I think going forward, rather than trying to fight with the vendor-specific prefixes we just go all in...
Thanks Jordon, just for the record we've tested the following browsers: - MacOS: - Chrome - Firefox - Safari - Windows: - Chrome - Firefox - Edge - Brave -...
My concern with this isn't so much a technical one, but one of education. Users will need to be informed that we diverge from Tailwind's recommend here. All their examples...