Skip to content
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

Input types discrepancy #15170

Open
desig9stein opened this issue Dec 12, 2024 · 1 comment
Open

Input types discrepancy #15170

desig9stein opened this issue Dec 12, 2024 · 1 comment
Assignees
Labels
🛠️ status: in-development Issues and PRs with active development on them ❓ question

Comments

@desig9stein
Copy link
Contributor

Question

In Angular, all input fields have type-search as in web components, only the standard input has it.

@sdimchevski, @simeonoff, If we make angular behave as the web components and only apply this to the standard input field it may introduce a visual breaking change for some users.

image

Web components also don't have line-type

image
@sdimchevski
Copy link

sdimchevski commented Jan 7, 2025

@simeonoff @desig9stein Using type="search" only for standard input fields adheres to best practices and avoids misusing the semantic intent of input types (e.g., search should logically only apply to search fields). As discussed on the daily today let's mirror what we have in Web Components. I guess we can warn developers in the Angular documentation or release notes that the behavior has changed.

Line input fields are considered outdated in Material Design 3 and have been replaced by filled and outlined text fields but in order not to introduce big visual braking changes we are keeping line type in Angular for now.

@simeonoff simeonoff assigned didimmova and unassigned desig9stein Jan 8, 2025
@didimmova didimmova added the 🛠️ status: in-development Issues and PRs with active development on them label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ status: in-development Issues and PRs with active development on them ❓ question
Projects
None yet
Development

No branches or pull requests

4 participants