Opened 13 years ago
Closed 11 years ago
#6059 closed bug (fixed)
Button: Primary icon "enabled" when button is disabled
| Reported by: | kvgeorge1 | Owned by: | tj.vantoll |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.9.1 |
| Component: | ui.button | Version: | 1.8.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When setting a button to state (disabled) in IE8 with a primary icon, the primary icon is not grayed-out like in IE6.
Change History (7)
comment:1 Changed 13 years ago by
comment:2 Changed 11 years ago by
| Milestone: | TBD → 1.11.0 |
|---|
comment:3 Changed 11 years ago by
| Owner: | set to bchiasson |
|---|---|
| Status: | new → assigned |
| Summary: | Button with primary icon when disabled still shows icon as enabled in IE8 → Button: Primary icon "enabled" when button is disabled |
| Type: | bug → feature |
comment:4 Changed 11 years ago by
| Owner: | changed from bchiasson to tj.vantoll |
|---|
IE8 has a bug where elements with relative/absolute positioning do not inherit the opacity value of their parents (http://seanmonstar.com/post/709013028/ie-opacity-ignores-positioned-children).
This can be fixed with the following:
.ui-state-disabled .ui-icon {
filter:Alpha(Opacity=35);
}
Example: http://jsfiddle.net/tj_vantoll/qMQN5/18/
I'm going to do a little more research to see if this problem applies to other things in UI before sending a pull request.
comment:5 Changed 11 years ago by
This problem also occurs on disabled inline datepickers. After discussion we couldn't think of any adverse effects of the fix shown in the above comment.
Pull request: https://github.com/jquery/jquery-ui/pull/771
comment:6 Changed 11 years ago by
| Milestone: | 1.11.0 → 1.9.1 |
|---|---|
| Type: | feature → bug |
comment:7 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
CSS: Apply opacity to absolutely positioned ui icons in IE8. Fixed #6059 - Button: Primary icon "enabled" when button is disabled.
Changeset: fe1ecf97e01f6b9e6041ae324deafb69063d1c9c
Further research shows that this happens when the DOCTYPE is specified as:
<!DOCTYPE html PUBLIC "-W3CDTD XHTML 1.0 StrictEN"
Setting DOCTYPE to <!DOCTYPE html> does not show the problem.