Function is_recognized_position_name 

pub fn is_recognized_position_name(s: &str) -> bool

Constat #8: PositionMode::Named(String) accepts any string, but ChildComponent::absolute_position only ever treats the literal "absolute" specially — every other value (including the CSS-legitimate "relative"/"static", which an LLM reasoning in CSS terms naturally reaches for) silently drops x/y: the component is taken out of flow (is_flow() is false for any Some(position)) but never receives an absolute offset either, since only "absolute" is matched. x/y are top-level sibling fields on ChildComponent, not on PositionMode itself, so this can’t detect whether they were actually set — only that, if they were, they are about to be silently ignored. "absolute" stays completely silent (the common, correct case); anything else warns.