The submenu that was never styled
Restoring a collapsed nav group exposed a specificity trap that had also been quietly shrinking every touch target on phones.
What we were doing. Putting a collapsible submenu back under Consulting & Services, to hold the two pages meant for people already in conversation with us: the A Friend Nearby case study and the Agent Services menu. Neither belongs on the homepage grid, so the drawer is the only place they live.
The markup was the only thing missing
The rebuild the night before had dropped the submenu markup but kept its JavaScript and its CSS, with a comment saying the styling stayed available for whenever a group wanted one. It turned out the styling had never worked.
The first render put the toggle at 17px tall with no padding, sitting several pixels left of the link above it. The cause is the drawer's own defense against host pages. That block restates a handful of selectors at id strength, #quantum-drawer button among them, zeroing border, margin and padding so a content page cannot reach in and restyle the nav. Everything the drawer actually wants is restored immediately below at the same strength — but only for the selectors that existed when it was written. .submenu-toggle was not one of them, so a plain class selector at (0,1,0) was losing to (1,0,1) every time.
The same trap, one tier down
Checking whether anything else was written against a selector the defense block restates turned up the touch tier:
@media (max-width: 640px), (pointer: coarse) {
.drawer-nav a { padding: 13px 12px; font-size: 0.95rem; }
}
A media query adds no specificity. That rule is (0,1,1) and it was losing to #quantum-drawer .drawer-nav a at (1,1,1), so the larger touch targets had never applied at any width. Measured at 375px, nav rows were computing to the desktop 7px/10px padding and standing 32px tall. After prefixing them they measure 44 to 45px.
One subtlety: the padding rule could not be raised on its own. .drawer-nav-plain a keeps Home, Contact and Newsletter a step smaller than the category links, and it can only outrank .drawer-nav a from equal specificity. Raising one without the other would have left the plain links quietly inheriting the larger size. Both moved together.
What to take from it
The defense block is worth its cost, but it sets a rule for the whole file: any new selector it also restates has to be written at id strength, or it will be silently ignored. Silently is the problem. Nothing errors, nothing logs, and the styles simply do not appear — which is why a submenu could sit in the stylesheet for a day looking finished, and a touch tier could sit there considerably longer.
Both were found by measuring computed styles in a browser rather than by reading the file. The CSS reads correctly. It is only the cascade that disagrees.