-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flux Input File Template Breaks with sr-only Class #701
Comments
Or should I Explicitly add the
|
Can you share a smaller reproducible code snippet? Preferably as a Volt component so it's easily copy/pasted. |
if you think, it is not an issue, then never mind. |
I'm asking because it's easier to help if you do so. You have |
I didn't wire anything, it is a fresh installation and just copied file input from flux docs |
I think I understand the issue. You're seeing a scrollbar outside the content div that's not there without the file input components. Is that what you mean? Because you only mentioned |
Exactly, because I think |
I think the issue is that you've added This doesn't feel like a Flux issue. |
The same thing will happen if you add |
That's a different issue, but it's not related to Flux. Tailwind is following the most accessible way make elements visible to screen readers only using I'm happy to help with Flux issues but this is a CSS issue somewhere in your own custom layout. |
Alright! I wonder why it solves when I add,
|
I really think FLUX FILE should have
|
You can add - <div class="sm:flex-1 sm:overflow-y-auto"
+ <div class="sm:flex-1 sm:overflow-y-auto relative"> I don't think |
This issue with sr-only is discussed adamwathan too, worth reading. |
The template breaks when using flux:input file inputs, particularly when the input tag has the sr-only class. This issue arises only when the content contains a significant amount of content, such as I use lorem2000 text to fillup the area.
Steps to Reproduce
Sample Template
Additional Notes and Suggested Fix
sr-only
class tohidden
resolves the issue.The text was updated successfully, but these errors were encountered: