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

field 60% width #3301

Closed
semoi opened this Issue Dec 19, 2011 · 9 comments

Comments

Projects
None yet
8 participants
@semoi

semoi commented Dec 19, 2011

When using he following code on "wide" screen, the label is on the left of the input field (that's ok).
The label have a 20% width.
But the input field have a 60% width. Why not 80% ?

                 <label for="name">Text Input:</label>
                 <input type="text" name="name" id="name" value=""  />
                </div>

@jblas

This comment has been minimized.

Show comment
Hide comment
@jblas

jblas Dec 19, 2011

Contributor

@semoi

What version of the framework are you using? @toddmparker, didn't we fix this for 1.0?

Contributor

jblas commented Dec 19, 2011

@semoi

What version of the framework are you using? @toddmparker, didn't we fix this for 1.0?

@semoi

This comment has been minimized.

Show comment
Hide comment
@evgenyneu

This comment has been minimized.

Show comment
Hide comment
@evgenyneu

evgenyneu Feb 22, 2012

+1 to @semoi
Is it a bug or was it supposed to be 60% If so, why?

+1 to @semoi
Is it a bug or was it supposed to be 60% If so, why?

@agcolom

This comment has been minimized.

Show comment
Hide comment
@agcolom

agcolom Feb 23, 2012

Member

This seems to be also the problem for #3486

Member

agcolom commented Feb 23, 2012

This seems to be also the problem for #3486

@ghost ghost assigned Wilto Feb 24, 2012

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Feb 24, 2012

Contributor

@Wilto will give these a look soon.

Contributor

toddparker commented Feb 24, 2012

@Wilto will give these a look soon.

@Wilto

This comment has been minimized.

Show comment
Hide comment
@Wilto

Wilto Mar 2, 2012

Contributor

Not gonna lie, this is one that has been bothering me for a while now. I’ve set up a branch where I’m working on making better use of the space available to the form widgets, and removing some of the fixed-width padding and whatnot in play. It’s a change that’s gonna impact a lot of places so I want to make sure we have time to test thoroughly. Not something I’d want to try sneaking into 1.1, but know that it’s in the works.

Contributor

Wilto commented Mar 2, 2012

Not gonna lie, this is one that has been bothering me for a while now. I’ve set up a branch where I’m working on making better use of the space available to the form widgets, and removing some of the fixed-width padding and whatnot in play. It’s a change that’s gonna impact a lot of places so I want to make sure we have time to test thoroughly. Not something I’d want to try sneaking into 1.1, but know that it’s in the works.

@evgenyneu

This comment has been minimized.

Show comment
Hide comment
@evgenyneu

evgenyneu Mar 6, 2012

I am using width: 78% and box-sizing: border-box (plus vendor prefixes) for inputs and textareas in widescreen mode. Works fine.

I am using width: 78% and box-sizing: border-box (plus vendor prefixes) for inputs and textareas in widescreen mode. Works fine.

@jakeboone02

This comment has been minimized.

Show comment
Hide comment
@jakeboone02

jakeboone02 Mar 8, 2012

Contributor

This is causing us some headaches with styles in our app, especially in the responsive design department (desktop width vs tablet width vs smartphone width). I know @Wilto's on the case but can we get a Medium or High priority tag on this ticket just to maintain visibility?

Contributor

jakeboone02 commented Mar 8, 2012

This is causing us some headaches with styles in our app, especially in the responsive design department (desktop width vs tablet width vs smartphone width). I know @Wilto's on the case but can we get a Medium or High priority tag on this ticket just to maintain visibility?

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Mar 8, 2012

Contributor

Done. This is tagged to the 1.2 milestone so it's definitely on our radar.

Contributor

toddparker commented Mar 8, 2012

Done. This is tagged to the 1.2 milestone so it's definitely on our radar.

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