) carrying a same-specificity !important box-shadow rule; on an
equal-specificity/!important tie CSS resolves by source order, so a -placed override
loses to the header's own later rule. Being last in the document guarantees this always wins. */
.dmRespRow, .dmRespColsWrapper, .dmRespCol,
.about-grid, .footer-info-grid, .footer-grid {
direction: ltr !important;
}
/* Header: replace drop-shadow with a thin beige bottom border (explicit design change) */
#dm .dmInner div.dmHeader,
#dm .dmInner div.dmHeader.u_hcontainer,
#dm .dmInner div.u_hcontainer,
#hcontainer {
box-shadow: none !important;
-moz-box-shadow: none !important;
-webkit-box-shadow: none !important;
border-bottom: 1px solid rgb(221, 205, 185) !important;
}
/* Modern contact-form (about page only — see script header comment): submit button onto its own
centered row. Scoped to the DIV-wrapper usage specifically: the about page's ".contact-form" is
a flex row with 3 ".form-group" fields + a ".form-submit" DIV wrapper as siblings, so the
submit button rendered inline with the fields until forced onto its own line. The contact page
reuses the class name ".form-submit" for something structurally different (the