/**
 * R7/D-07/D-08 (14-01): restores Flatsome's normal theme header/footer on
 * the full-page `[exprez_designer]` route (locked user decision,
 * 2026-07-19 — reverses 13-06's chrome-less full-viewport takeover) and
 * widens the Flatsome content column to full width so the designer fills
 * the content area between the header and footer, regardless of which
 * page template the admin selected for the shortcode page.
 *
 * Keyed off the SAME `exdz-fullpage-designer` body class
 * `Shortcodes\DesignerShortcode::maybe_add_fullpage_body_class()` already
 * adds ONLY on a page carrying the `[exprez_designer]` shortcode — a
 * reversal in place, not a new mechanism (RESEARCH Bucket A "Exact
 * Reversal Path" step 2).
 *
 * These rules deliberately live OUTSIDE editor-src/src/styles/editor.css
 * (which stays .exdz-root-scoped, exdz-prefixed only, T-13-16) — they
 * target THEME elements (Flatsome's own content-column wrappers), not this
 * plugin's own editor chrome.
 *
 * Defense-in-depth only (RESEARCH Pitfall 1): if the shortcode page uses
 * Flatsome's default `page.php` template (which wraps `the_content()` in a
 * `.row.row-main > .large-12.col > .col-inner` column that clamps to the
 * theme's boxed container max-width — see `page.php:19-21` vs the
 * `page-blank.php` "Page - Full Width" template, which has no such
 * wrapper), these rules widen that column to full width so the designer is
 * full-width even without the admin selecting the "Page - Full Width"
 * template. This stylesheet ships no chrome-hiding rule for `#header`,
 * `.footer-wrapper`, or `#footer` — those render normally now (locked
 * decision).
 */
body.exdz-fullpage-designer #content.content-area .row.row-main,
body.exdz-fullpage-designer #content.content-area .large-12.col,
body.exdz-fullpage-designer #content.content-area .col-inner {
    max-width: none;
    width: 100%;
}