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

remove css not selector - incompatible with ie8 #1061

Merged
merged 1 commit into from Jan 7, 2013

Conversation

butonic
Copy link
Member

@butonic butonic commented Jan 2, 2013

the 'not' selector is only supported since IE9+, we are overriding the checkbox margin and with later anyway, so this should not produce any regressions

@butonic
Copy link
Member Author

butonic commented Jan 2, 2013

@DeepDiver1975 do you know who I can notify for ie8 testing?

@DeepDiver1975
Copy link
Member

me 😈

@DeepDiver1975
Copy link
Member

tested in the login screen 👍
any other screen to test?

@@ -34,7 +34,7 @@ filter:progid:DXImageTransform.Microsoft.gradient( startColorstr='#35537a', endC

/* INPUTS */
input[type="text"], input[type="password"] { cursor:text; }
input:not([type="checkbox"]), textarea, select, button, .button, #quota, div.jp-progress, .pager li a {
input, textarea, select, button, .button, #quota, div.jp-progress, .pager li a {
width:10em; margin:.3em; padding:.6em .5em .4em;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will break other browsers. 10em wide checkboxes don't look that cool ;)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in line 51 there is a input[type="checkbox"] { margin:0; padding:0; height:auto; width:auto; } which overrides this one. the other browsers will not suffer from this. It is basically redundant.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe also simply remove width:10em;. I see no need for it in a what should be a generic stylesheet.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jancborchardt how can we systematically clean up the css? any ideas? you ok with this PR?

@tanghus
Copy link
Contributor

tanghus commented Jan 2, 2013

Sorry 👎 Is there a way we can make a fallback for IE8 that won't break it for other browsers @jancborchardt ?

btw, shouldn't it be input:not([type="checkbox"]):not([type="radio"])?

@DeepDiver1975
Copy link
Member

Is that a possible solution: http://dean.edwards.name/weblog/2010/03/ie7js-update/

@tanghus
Copy link
Contributor

tanghus commented Jan 2, 2013

Interesting. Especially because it would only load in the crappy browsers.

@butonic
Copy link
Member Author

butonic commented Jan 2, 2013

@tanghus before starting to add fallbacks shouldn't we first/finally add Modernizr? @karlitschek what is the status there?

@tanghus
Copy link
Contributor

tanghus commented Jan 2, 2013

@butonic Eh, I kinda promised to submit a pull request on that, but I blame it on the holidays ;)

@jancborchardt
Copy link
Member

Big thanks @butonic! I actually discovered I can’t get the Windows machine I have access to to run IE8. Do we have any remotely accessible virtual machines for testing?

@butonic
Copy link
Member Author

butonic commented Jan 4, 2013

@jancborchardt @tanghus do you give me your 👍 as this currently fixes the css?

@tanghus
Copy link
Contributor

tanghus commented Jan 4, 2013

👍

butonic added a commit that referenced this pull request Jan 7, 2013
…_ie8_input_fields

remove css not selector - incompatible with ie8
@butonic butonic merged commit 3dbb148 into master Jan 7, 2013
@DeepDiver1975 DeepDiver1975 deleted the remove_css_not_selector_to_fix_ie8_input_fields branch January 7, 2013 09:50
@lock lock bot locked as resolved and limited conversation to collaborators Aug 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants