search

oulan / iui

Automatically exported from code.google.com/p/iui
MIT License
0 stars 0 forks source link

Dialog CSS affects others / CSS "not" doesn't work? / Inputs aren't styled correctly #293

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
To begin with: iOS 4.3.3 on iPhone 3Gs

What steps will reproduce the problem?
1. Create a form with input values.
2. Notice that CSS intended for dialogs affects non-dialog input elements.

What is the expected output? What do you see instead?
I would like to see the input elements conform to whatever the iOS style for 
their location normally would be.  For inputs outside dialogs, this is normal 
size Helvetica font with a bluish tint.

I got around this by modifying iui.css (line ~245?) from:
input:not(input[type|=radio]):not(input[type|=checkbox]) {
to:
.dialog > input:not(input[type|=radio]):not(input[type|=checkbox]) {

I also added the following to make the inputs look and behave like they 
should--iui.css (line ~302)--unfortunately the "not" pseudo-class does not 
appear to work for my version of MobileSafari (iOS 4.3.3). In order to get 
these stylesheet rules to work I had to remove the nots:
.row > input:not(input[type|=radio]):not(input[type|=checkbox]) {
to:
.row > input {
    ...
    color: #385487;
    -webkit-appearance: none;
    font-size: 16px;
}

But unfortunately I'm not sure if this is going to affect things like toggles 
and stuff yet.

Original issue reported on code.google.com by eslind...@gmail.com on 30 Jul 2011 at 3:09

GoogleCodeExporter commented 9 years ago 
This is related to Issue #256 and is probably a duplicate.

Original comment by msgilli...@gmail.com on 25 Sep 2011 at 10:25

GoogleCodeExporter commented 9 years ago 
Actually, Issue #256 covers the problem with the CSS :not pseudo-class and the 
fix for that.

I see you added ".dialog > " to the front of the selector to make it more 
specific.

Original comment by msgilli...@gmail.com on 25 Sep 2011 at 11:07

GoogleCodeExporter commented 9 years ago 
Yeah sorry I probably should not have put more than one problem in a single 
issue.

Original comment by eslind...@gmail.com on 25 Sep 2011 at 11:49