GitShow/tailwindlabs/tailwind-plus-issues
tailwindlabs

tailwind-plus-issues

A place to report bugs discovered in Tailwind Plus.

by tailwindlabs
Star on GitHubFork
253 stars4 forks4 contributorsQuiet · 11mo agoSince 2020

Meet the team

See all 4 on GitHub →
reinink
reinink7 contributions
adamwathan
adamwathan4 contributions
thecrypticace
thecrypticace1 contribution

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

1 of 6 standards met

Community profile →
37
✓README○License○Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 13 discussions · Last activity 11mo ago
See all on GitHub →
jensdenies
Full-width flyout menu is not responsiveOpenIssue

What component (if applicable) URL for category: https://tailwindcss.com/plus/ui-blocks/marketing/elements/flyout-menus Component name: Full-width Describe the bug This component looks completely broken on mobile, it is not responsive while the other components are. To Reproduce Steps to reproduce the behavior: 1. Go to the component 2. Reduce the screen to mobile size Expected behavior I think it should be responsive Screenshots**

jensdenies · 14h ago
mdhender
UI Template download archives older version than live pagesOpenIssue

What component (if applicable) URL for category: https://tailwindcss.com/plus/ui-blocks/marketing Component name: Applies to Marketing, Application UI, and E-Commerce archives. Describe the bug The downloaded archive is v4. The live pages are v4.3. There's no CHANGELOG in the archives to help identify changes. To Reproduce Steps to reproduce the behavior: 1. Go to 'https://tailwindcss.com/plus/ui-blocks/marketing' 2. Click on 'Download' 3. Marketing v4 ZIP file will download. 4. The live pages contain v4.3. 5. It's not clear what, if anything, has changed because the live pages have extra code for system/dark/light mode. Expected behavior The downloaded ZIP file would contain the same version of templates as the live site or a CHANGELOG with recent updates so that it's easier to find changes. Screenshots N/A Browser/Device (if applicable) N/A Additional context** Not really a bug. Nice to have, not a blocker by any means.

mdhender · 1d ago
gencher
Catalyst Dialog closes when dragging the browser scrollbar (outside click triggered)OpenIssue

Component (if applicable) URL: https://catalyst.tailwindui.com/docs/dialog#with-scrolling-content Component: Dialog (with scrolling content) Describe the bug In the “With scrolling content” Dialog example, clicking/dragging the browser/page scrollbar while the dialog is open causes the dialog to close. It looks like the scrollbar interaction is being treated as an outside click and triggers . To Reproduce 1. Go to https://catalyst.tailwindui.com/docs/dialog#with-scrolling-content 2. Open the “Terms and conditions” dialog 3. Instead of scrolling inside the dialog, click and drag the browser’s right scrollbar (page scrollbar) 4. Release the mouse → the dialog closes Expected behavior Dragging/clicking the browser/page scrollbar should not close the dialog. Only an intentional outside click (on the backdrop) or Escape should close it. Actual behavior Dialog closes on scrollbar drag/release, as if an outside click happened. Browser/Device OS: macOS Browser: Firefox Additional context** We are using the Catalyst template in our app as well, and we can reproduce the exact same behavior there (Headless UI Dialog). So this is not only the docs site — it affects real Catalyst-based apps too.

gencher · 3w ago

Recent fixes

View closed PRs →
MichaHuhn
Feature request (docs): Add guide on how to load Inter font locallyClosedIssue

Currently, the docs only explain how to load the Inter font via the CDN. It would be great to add a short guide on how to load it locally.

MichaHuhn · 2d ago
gartenkralle
Usability issue in el-dialog of elements.jsClosedIssue

v4.3.0, cli, debian When I do mouse down on el-dialog and mouse up outside the el-dialog (like for selecting text) the dialog closes. This is an unexpected behavior.

gartenkralle · 4w ago
tomazartack
El-select and El-dropdown which is received in Ajax call is not initialisedClosedIssue

Hello, in my website I have an ajax request, which renders some html, and the content is then inserted into a main page's div element, a container. However, the content received during ajax also includes a tailwind elements such as el-select or el-dropdown. Documentation here: https://tailwindcss.com/plus/ui-blocks/application-ui/elements/dropdowns I have a script tag which includes elements library (as seen in documentation), which works on el-selects and el-dropdowns which are present in initial page load, but click events do not work on elements received in ajax calls. How can I initialise these newly received el-dropdown and el-select elements?

tomazartack · 1mo ago
Structured data for AI agents

Repository: tailwindlabs/tailwind-plus-issues. Description: A place to report bugs discovered in Tailwind Plus. Stars: 253, Forks: 4. Open PRs: 0, open issues: 13. Last activity: 11mo ago. Community health: 37%. Top contributors: reinink, adamwathan, thecrypticace.

·@ofershap

Replace github.com with gitshow.dev