Steve, thanks for posting about this issue and leading the charge to change to the specification. I completely agree - it is a big limitation. The networkDuration is a great addition, but how about getting this further and removing the Timing-Allow-Origin header requirement? The data the API provides does not contain any private data about the end user or the URL, or the interaction between the two, so what is it really protecting?
- Re: add "ne... Ilya Grigorik
- Re: add "ne... Steve Souders
- Re: add "ne... Ilya Grigorik
- Re: add "ne... Steve Souders
- Re: add "ne... Patrick Meenan
- Re: add "ne... Ilya Grigorik
- Re: add "ne... Steve Souders
- Re: add "ne... Ilya Grigorik
- Re: add "ne... Steve Souders
- Re: add "ne... Ilya Grigorik
- Re: add "networkDuration" to Res... Ryan Pellette
- RE: Re: add "networkDuration&quo... Aaron Heady (BING AVAILABILITY)
- RE: Re: add "networkDuration" to... Ryan Pellette
- RE: RE: Re: add "networkDuration... Aaron Heady (BING AVAILABILITY)
- Re: add "networkDuration" to Res... Todd Reifsteck
- Re: add "networkDuration" t... Ilya Grigorik
- RE: add "networkDuration&quo... Todd Reifsteck
- Re: add "networkDuration... Ilya Grigorik