Tweet · 30 Sept 2016, 18:08 UTC

@elrond25 Again, please read the thread. The intent may look good but it’s just lying about the W3C’s behaviour and the source of the issue.