Skip to main content

Search and Top Navigation

#10673 closed bug (notabug)

Opened October 23, 2014 05:58PM UTC

Closed October 23, 2014 06:04PM UTC

Last modified October 24, 2014 06:34PM UTC

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:
.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.

Attachments (0)
Change History (4)

Changed October 23, 2014 06:04PM UTC by scottgonzalez comment:1

resolution: → notabug
status: newclosed

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.

Changed October 24, 2014 05:50PM UTC by bob-gray comment:2

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?

Changed October 24, 2014 06:15PM UTC by bob-gray comment:3

This was a change in behavior. It worked in 1.10 because the scope was applied to all the rules and not just some.

Changed October 24, 2014 06:34PM UTC by scottgonzalez comment:4

Can you please provide a jsbin or jsFiddle showing the problem you're talking about?