When Chrome, Firefox, and Safari All Agree, the Spec Is the One That Changes
Browsers situationship: When browsers agree but the spec doesn't

When browsers agree on behavior that contradicts the written specification, the fix isn't always three browser bugs. Sometimes the spec itself gets updated. Drawing on a real case where newline normalization in HTML form submissions diverged from the spec, this piece explores how browser implementations and specifications co-evolve, why convergence matters more than correctness, and how the Web's memory turns old bugs into compatibility constraints.
All browsers agree to normalize the newlines, but the spec would have them without normalization.