3 ms·
The Chromium bug is a demonstration of the fact that different behaviors in different implementations can lead to real bugs. There's no reason to think that one
by eridius 9y ago
The Chromium bug is a demonstration of the fact that different behaviors in different implementations can lead to real bugs. There's no reason to think that one Chromium bug is the only time this will ever matter.
- Dylan16807 9y agoIt says in the spec that the number of replacement characters can vary, so it's hard to blame Unicode for a bug caused by two parsers making different numbers. (Unless the argument is that there should be an official required number, which is a different discussion entirely.)
- eridius 9y agoNo, you're right in that it's perfectly legitimate for multiple parsers to behave differently here. But if there's one behavior that nearly all parsers have standardized on, that's very valuable because it makes it a lot easier to use two different parsers without a problem.