#10673 closed bug (notabug)
CSS Scope increases specificity and breaks cascade causing unintended borders
| Reported by: | bob-gray | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | ui.css-framework | Version: | 1.11.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
.ui-tabs .ui-tabs-nav li .ui-tabs .ui-tabs-panel .ui-dialog .ui-dialog-content .ui-dialog .ui-dialog-buttonpane .ui-slider .ui-slider-range /* maybe others */
All have border rules that should override .ui-widget-content border rule but they don't because of the extra specificity of <my-scope> .ui-widget-content.
Change History (4)
comment:1 Changed 8 years ago by
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
comment:2 Changed 8 years ago by
Maybe this is an issue with the theme roller but I expected not to have the theme broken because I added a css scope before downloading. Why else would adding a css scope be an option?
comment:3 Changed 8 years ago by
This was a change in behavior. It worked in 1.10 because the scope was applied to all the rules and not just some.
comment:4 Changed 8 years ago by
Can you please provide a jsbin or jsFiddle showing the problem you're talking about?
Note: See
TracTickets for help on using
tickets.
I'm not sure how you expect scoping in CSS to work other than the way it does. Anyway, scoping is not part of jQuery UI, it's just a feature of ThemeRoller.