Rethink spec compliance

[TimothyGu]

In #181, I laid out the reasons for specific choices in spec compliance (or lack thereof). The most significant factor in my decisions was compatibility with existing implementations (github/fetch, Chrome, and Firefox).

However, github/fetch has recently adopted the new spec behavior in their v2 release (see JakeChampion/fetch#429); so has Firefox in v52 (see release notes), which will ship in March 2017.

I think we should remove the global FOLLOW_SPEC option and make it the only behavior.

[bitinn]

Seem reasonable, v2.0 alpha is a good time to do that. (From my phone)

…

在 2017年1月23日，07:44，Timothy Gu ***@***.***> 写道： In #181, I laid out the reasons for specific choices in spec compliance (or lack thereof). The most significant factor in my decisions was compatibility with existing implementations (github/fetch, Chrome, and Firefox). However, github/fetch has recently adopted the new spec behavior in their v2 release (see JakeChampion/fetch#429); so has Firefox in v52 (see release notes), which will ship in March 2017. I think we should remove the global FOLLOW_SPEC option and make it the only behavior. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.