(Select) select options does not fully responsive
See original GitHub issueBug, feature request, or proposal:
[ x ] Bug
What is the current behavior?
At the first show the select options
, the cdk calculate width for select options, after that when user resize (rotate screen on mobile) the cdk does not recalculate again. So the width of select options is overflowing the container.
What is the expected behavior?
The width of select options is adaptive.
What are the steps to reproduce?
Resize this page:
https://angular-dynamic-forms.firebaseapp.com/
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:12
Top Results From Across the Web
Options in select box not responsive - Stack Overflow
Try to change the CSS property for select and option attr in your form: CSS: #a_idarticle, #a_idarticle option { text-overflow: ellipsis; }.
Read more >Chose Option (Variation selection) drop down not responsive ...
This responsiveness issue might be caused by a conflict with your theme or with another plugin, and that would cause that misalignment.
Read more >CSS · Bootstrap
It includes predefined classes for easy layout options, as well as powerful ... and <select> elements with .form-control are set to width: 100%;...
Read more >Select API - Material UI - MUI
Name Type Default
autoWidth bool false
children node
classes object
Read more >About responsive search ads - Google Ads Help
Next, in any given ad, a maximum of 3 headlines and 2 descriptions will be selected to show in different combinations and orders....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hey any chance to fix dis?