Skip to content

[Bug]: Outlined Input style broken in v2.2.2 #620

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

Open
3 tasks done
vhrmo opened this issue Apr 28, 2025 · 1 comment
Open
3 tasks done

[Bug]: Outlined Input style broken in v2.2.2 #620

vhrmo opened this issue Apr 28, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@vhrmo
Copy link

vhrmo commented Apr 28, 2025

Before submitting...

Context

As you can see on shaphost from the documentation page - the outline line draws over the label text. Error state display overlaps the input field.

Image

Current Behavior

No response

Expected behavior

No response

Possible Solutions or Causes

The issue was introduced by commit: d259c96

fix: only move dropdown on init

This fixes also the select issue with the label placement. The impact
is not tested, but in that case we should offer a relocate function to
move the dropdown manually.

This change in _input-fields.scss:185 fixes the issue but I didn't test the fix above which may be impacted by this:

- background-color: transparent; //(--md-sys-color-background); 
+ background-color: var(--md-sys-color-background);

Steps to reproduce

No response

Your Environment

  • Version used: 2.2.2
  • Browser Name and version: Google Chome & Firefox
  • Operating System and version (desktop or mobile): MAC desktop
  • Additional information you want to tell us:
@vhrmo vhrmo added the bug Something isn't working label Apr 28, 2025
@wuda-io
Copy link
Member

wuda-io commented May 4, 2025

Yes, thats correct that the outline styles are broken atm, but it has to work with transparent background in future too!

So it will hopefully be fixed with the next version. Check out PR #607 to stay up to date. This will unfortunately need a refactoring of the input fields for existing projects.

Also the docs will be covered in markdown inside the core repo itself for each component, so it will be a lot easier to maintain and helps keeping the docs in sync with the actual code of the lib.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants