It's very troubling, because the decoupling of resources from their representations is so core to HTTP.

A year ago, the maintainers defended Chrome's behavior as consistent with Firefox, and vaguely as consistent with the spec. Since then, more complaints have piled up and those original defenses have been deconstructed (Firefox no longer exhibits this spec-breaking behavior, multiple unmet sections of the spec have been cited). But for the last 9 months, the maintainers have not said a thing, despite doing various house-cleaning chores on the bug report itself.

One can't help but wonder if there's some ulterior motive for ignoring the community and keeping the WontFix status, though nothing obvious comes to mind... The impact this could have and the way they've handled this is reminiscent of how the downfall of a different browser began.