It seems to me that this comment was the driver for this Chrome "feature." The problem as I see it is that the Chrome devs are fixing it at the wrong place. Ch

It seems to me that this comment was the driver for this Chrome "feature." The problem as I see it is that the Chrome devs are fixing it at the wrong place. Changing one user app, when the standards state it's necessary to include just breaks things. They need to change the standard, not the app. Until then, they've just got a broken implementation.