Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Match whitespace for custom property serialization #10318
When serializing custom properties, they must be preserved exactly as authored (https://crbug.com/661854). variable-invalidation.html added additional whitespace to the expectation, going against this part of the spec. This change makes the test pass in Firefox, Chrome, and Edge.
I believe that the working group has resolved to something different that, when parsing, whitespaces are trimmed from start and end of token stream, and when serializing, a whitespace is always added after the colon.
The specs may need some update if they haven't been, so do implemenations.