Important: this article describes a problem that cannot be reproduced with Google Chrome, only with Firefox and Edge (I did not test with other bro...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for this. This is great. I'm not convinced though that Chrome's deviation is an intervention. If it were it'd expect it to be better documented with a clear description of exactly what the nature of the deviation was, so that other browsers could copy it, and the spec amended to due course. But the linked article seems unsure whether it is intentional and provides no description or link to a precise definition.
I'm not so sure either. However it's not so uncommon to see Chrome deviating from standards when it suits them.
The good thing about using Firefox as my main browser is that I can catch a lot of weird "bugs" (in fact, things working as specified) that otherwise would go unnoticed on Google Chrome.