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

[Form][Dropdown] <select> and initialized .ui.dropdown elements have incorrect heights when used inside a form with a specific size, e.g. .tiny #5154

Open
zerolfc opened this issue Mar 11, 2017 · 3 comments

Comments

@zerolfc
Copy link

zerolfc commented Mar 11, 2017

The select / dropdown height is not the same as the other input on ui small form

https://jsfiddle.net/zerolfc/oed27geb/

<form class="ui form tiny" role="form">
<div class="two fields">

                    <div class="field">
                        <label>Gender</label>
                        <select class="ui dropdown">
                            <option value="0">Female</option>
                            <option value="1">Male</option>
                        </select>
                    </div>

                    <div class="field">
                        <label>Telephone</label>
                        <input type="text">
                    </div>

                </div>
</form>

sematic-form-mini

@awgv awgv added this to the Needs Milestone milestone Mar 11, 2017
@awgv awgv changed the title Select / dropdown height [Form][Dropdown] <select> and initialized .ui.dropdown elements have incorrect heights when used inside a form with a specific size, e.g. .tiny Mar 11, 2017
@awgv
Copy link
Member

awgv commented Mar 11, 2017

It seems to be inconsistent with other sizes as well; if you initialize a dropdown that’s inside a .tiny form, it’s height will match other inputs, but:

  • I don’t think dropdowns should be initialized to inherit a form’s size variation.
  • It won’t work with other sizes, for example, if you initialize a dropdown that’s inside of a .big form, its height will still be incorrect.

@stale
Copy link

stale bot commented Jun 5, 2018

There has been no activity in this thread for 90 days. While we care about every issue and we’d love to see this fixed, the core team’s time is limited so we have to focus our attention on the issues that are most pressing. Therefore, we will likely not be able to get to this one.

However, PRs for this issue will of course be accepted and welcome!

If there is no more activity in the next 90 days, this issue will be closed automatically for housekeeping. To prevent this, simply leave a reply here. Thanks!

@lubber-de

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants