Summary
8.1.7 changed WebUI/war/css/perc_decoration.css so CMS editor (and often preview) force the legacy fixed region grid with !important:
.vspan_2 { height : 120px !important; min-height: 0 !important; }
/* … vspan_4/6/8 … */
.hspan_2 { width : 160px !important; }
/* … including .hspan_12 { width : 960px !important; } … */
Intent: win over default theme.css min-height after the #757 footer fix so editor placeholders/footer stay put.
Regression: Most customers use responsive themes that set:
.vspan_* { height: auto }
.hspan_* { width: auto }
Decoration loads with the theme in editor/preview, so product !important overrides those rules. Published often stays fine (no decoration on live HTML); editor + preview look broken (clipped header regions, forced ~960px width, wrong layout).
A more correct fix would likely have used auto (or non-forcing) region sizing in decoration rather than hard-locking the old Percussion pixel grid with !important. Most sites are not on the stock fixed grid anymore.
Customer confirmation
- https://www.cloud.edu/ (Cloud County Community College)
- Theme
Cloud-County-CC/cccc-theme.css uses height: auto / width: auto on all vspan/hspan classes
- Post-8.1.7: editor + preview broken; published OK
- Confirmed fix: theme counter-override with
height/width: auto !important restoring responsive regions in CMS chrome
Proposed fix (8.1.x / this repo)
- Revisit
perc_decoration.css region rules: remove !important fixed pixel grid, or switch to auto / placeholder-only sizing that does not fight responsive themes.
- Keep published #757 behavior for default theme if still required (
min-height growth)—do not require every customer theme to absorb the editor pixel grid.
- Ship release note + short support snippet for sites already on 8.1.7+ until a patch lands.
- Test: responsive theme with span
auto — editor/preview match published layout intent.
Acceptance criteria
Related
Summary
8.1.7 changed
WebUI/war/css/perc_decoration.cssso CMS editor (and often preview) force the legacy fixed region grid with!important:Intent: win over default theme.css
min-heightafter the #757 footer fix so editor placeholders/footer stay put.Regression: Most customers use responsive themes that set:
Decoration loads with the theme in editor/preview, so product
!importantoverrides those rules. Published often stays fine (no decoration on live HTML); editor + preview look broken (clipped header regions, forced ~960px width, wrong layout).A more correct fix would likely have used
auto(or non-forcing) region sizing in decoration rather than hard-locking the old Percussion pixel grid with!important. Most sites are not on the stock fixed grid anymore.Customer confirmation
Cloud-County-CC/cccc-theme.cssusesheight: auto/width: autoon all vspan/hspan classesheight/width: auto !importantrestoring responsive regions in CMS chromeProposed fix (8.1.x / this repo)
perc_decoration.cssregion rules: remove!importantfixed pixel grid, or switch toauto/ placeholder-only sizing that does not fight responsive themes.min-heightgrowth)—do not require every customer theme to absorb the editor pixel grid.auto— editor/preview match published layout intent.Acceptance criteria
autothemes no longer need a customer!importantoverride to look correct in editor/previewRelated