Skip to content

Fix broken dropdowns, prepare v0.5.1#139

Merged
bgentry merged 2 commits intomasterfrom
bg-fix-broken-dropdowns
Sep 1, 2024
Merged

Fix broken dropdowns, prepare v0.5.1#139
bgentry merged 2 commits intomasterfrom
bg-fix-broken-dropdowns

Conversation

@bgentry
Copy link
Copy Markdown
Contributor

@bgentry bgentry commented Sep 1, 2024

The bug reported in #138 appears to have been caused by a headless UI upgrade (tailwindlabs/headlessui#3386), and only manifests itself in production builds. Downgrading the dependency to v2.1.1 fixes it.

I also turned on sourcemap builds for prod, because these might make debugging future issues easier and they'll only get loaded when opening the devtools anyway.

Preparing a v0.5.1 release as part of this fix to ship it ASAP.

@bgentry bgentry requested a review from brandur September 1, 2024 20:59
@bgentry bgentry merged commit 3fc0192 into master Sep 1, 2024
@bgentry bgentry deleted the bg-fix-broken-dropdowns branch September 1, 2024 21:06
bgentry added a commit that referenced this pull request Sep 2, 2024
The issue in #138 (fixed by #139) was the result of positioning the
listbox using tailwind classes instead of the `Listbox`'s own attrs for
positioning. Using the builtin positioning option seems to have fixed
this even on the latest version.
bgentry added a commit that referenced this pull request Sep 2, 2024
The issue in #138 (fixed by #139) was the result of positioning the
listbox using tailwind classes instead of the `Listbox`'s own attrs for
positioning. Using the builtin positioning option seems to have fixed
this even on the latest version.
bgentry added a commit that referenced this pull request Sep 2, 2024
* rely on builtin Listbox positioning + z-index class

* re-upgrade headless UI w/ positioning fixes

The issue in #138 (fixed by #139) was the result of positioning the
listbox using tailwind classes instead of the `Listbox`'s own attrs for
positioning. Using the builtin positioning option seems to have fixed
this even on the latest version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant