07:03, 25 July 2017, Jiankang Yao <yaojk@cnnic.cn>:

From: Mark Svancarek
Date: 2017-07-25 08:22

>But I don't understand why one would resist changing a spec which is known to be "wrong" and non-RFC compliant. Is the argument that revising it to be RFC-compliant would risk destabilizing more sites than fixing it?
>

Roughly, yes. Specifically, putting something in the spec that doesn't work in reality is unhelpful for developers who read it and try to implement based on that. A lot more web developers, and people who write guidance they use, are reading the spec than browser coders...

Cheers

Chaals

+1

I share the same concern with you.

Jiankang Yao

_______________________________________________
UA-EAI mailing list
UA-EAI@icann.org
https://mm.icann.org/mailman/listinfo/ua-eai

Private mail - Chaals is Charles McCathie Nevile - Standards Declaimer