|
|
|
|
|
|
by modeless
1417 days ago
|
|
|
No other browser has implemented it either. So it's not as though Chrome alone is preventing this feature from existing. It seems likely that other browsers might also take issue with it. It probably shouldn't have been finalized in the spec before being implemented at all anywhere. It may not have been well thought out. |
|
|
> We discussed this at the HTTP workshop:
> 1. It's okay to expose trailer headers sans semantics in the API and browsers are okay with that.
So it was discussed, and presumably at least well thought out enough that browsers were on board with it. Then, Chrome changed their mind, it was removed from the spec, and yeah, then other browsers didn't implement it either. But I wouldn't call it "likely" that they would have taken issue with it, as there was evidence to the opposite.