of four
(17px each) plus a
120px
, against nothing at all in the same position on production.
Not fixed in the markup, because wpautop runs at render time on content the
extractor never sees — the
s do not exist in extracted/contact-us.html.
Scoped inside .entry-content form so it cannot affect real body copy. */
.entry-content form br { display: none; }
.entry-content form p:has(> input[type="hidden"]) {
margin: 0;
line-height: 0;
}
/* Same root cause, a second shape of it: wpautop also leaves a genuinely EMPTY
`
` between every field's label and its input. It has no content and no
height of its own, so it is invisible — but it carries the 24px paragraph
margin, and there is one per field.
Measured: a text field row is 90px on production and was 104px here; ~14
fields per form, which is the whole of the +7.6% / +11.0% gap that appeared
on the two long forms the moment the field metrics themselves became
correct. A defect that only becomes visible once a bigger one is fixed.
Like the
rule above this cannot be fixed in the markup — the empty
does not exist in extracted/*.html, wpautop synthesises it at render. */
.entry-content form p:empty { display: none; }
/* --- 10.12 Consent fieldset metrics --------------------------------------
The TCPA/email consent blocks are the last of the /contact-us/ gap. Measured
on production vs staging at 1440px, field_9_8 (sms consent):
production fieldset h=197 label 12px/22px, h=198 no visible legend
staging fieldset h=309 label 16px/23.8px, h=238 legend h=24
Our label inherits the form's 16px where production sets 12px, so the same
consent copy takes four extra lines, and we additionally render a