On Thu, Jan 26, 2012 at 1:46 AM, David Bruant wrote:
> Le 26/01/2012 10:35, Boris Zbarsky a écrit :
>> On 1/26/12 9:12 AM, Adam Barth wrote:
Should the speculative parser have knowledge of?
>>>
>>> That's not what's currently specified. Like many other browser
>>> features, this feature
Le 26/01/2012 10:35, Boris Zbarsky a écrit :
On 1/26/12 9:12 AM, Adam Barth wrote:
Should the speculative parser have knowledge of?
That's not what's currently specified. Like many other browser
features, this feature lets web sites detect that the browser is
speculatively prefetching resourc
On Thu, Jan 26, 2012 at 1:35 AM, Boris Zbarsky wrote:
> On 1/26/12 9:12 AM, Adam Barth wrote:
>>> Should the speculative parser have knowledge of?
>>
>> That's not what's currently specified. Like many other browser
>> features, this feature lets web sites detect that the browser is
>> speculativ
On 1/26/12 9:12 AM, Adam Barth wrote:
Should the speculative parser have knowledge of?
That's not what's currently specified. Like many other browser
features, this feature lets web sites detect that the browser is
speculatively prefetching resources. If that's a big issue, it's
something we
On Sun, Jan 1, 2012 at 10:55 PM, Simon Pieters wrote:
> On Sat, 31 Dec 2011 19:11:53 +0100, Adam Barth wrote:
>> The policy for a given network fetch is determined when the fetch is
>> made. In this case, the request for a.css will include the Referer
>> header. If you move the tag above the
On Thu, 05 Jan 2012 18:37:05 +0100, Boris Zbarsky wrote:
On 1/2/12 1:55 AM, Simon Pieters wrote:
What about:
...and the browser speculatively fetches the stylesheet before the
element is in the DOM? Should the speculative parser have
knowledge of ?
I would say it should handle this j
On 1/2/12 1:55 AM, Simon Pieters wrote:
What about:
...and the browser speculatively fetches the stylesheet before the
element is in the DOM? Should the speculative parser have
knowledge of ?
I would say it should handle this just like it handles tags,
whether that's through keeping t
On Sat, 31 Dec 2011 19:11:53 +0100, Adam Barth wrote:
Another concern is what should happen if a request is sent before
finding a meta referrer. For instance:
In what conditions should the request for the css file be done? Ignore
the meta tag? Wait until the end of in case there woul
On Sat, 31 Dec 2011 19:54:27 +0100, David Bruant
wrote:
Le 31/12/2011 19:46, Adam Barth a écrit :
On Sat, Dec 31, 2011 at 10:30 AM, David Bruant
wrote:
I think there could be a use case for same-origin+fragment-less URL
which allows for "internal" tracking but not external tracking.
Yeah
Le 31/12/2011 19:46, Adam Barth a écrit :
> On Sat, Dec 31, 2011 at 10:30 AM, David Bruant wrote:
>> I think there could be a use case for same-origin+fragment-less URL
>> which allows for "internal" tracking but not external tracking.
> Yeah, that makes sense. I'm not sure whether we need to ha
On Sat, Dec 31, 2011 at 10:30 AM, David Bruant wrote:
> Le 31/12/2011 19:11, Adam Barth a écrit :
>> On Sat, Dec 31, 2011 at 9:44 AM, David Bruant wrote:
>>> Hi,
>>>
>>> My feedback regards the current version of the wiki page [1].
>>>
>>> I'm curious about why a Referer header is always sent. Sp
Le 31/12/2011 19:11, Adam Barth a écrit :
> On Sat, Dec 31, 2011 at 9:44 AM, David Bruant wrote:
>> Hi,
>>
>> My feedback regards the current version of the wiki page [1].
>>
>> I'm curious about why a Referer header is always sent. Specifically for
>> "never", an empty string is sent. Why not jus
On Sat, Dec 31, 2011 at 9:44 AM, David Bruant wrote:
> Hi,
>
> My feedback regards the current version of the wiki page [1].
>
> I'm curious about why a Referer header is always sent. Specifically for
> "never", an empty string is sent. Why not just not send the header at
> all?
Oh, the intent is
Hi,
My feedback regards the current version of the wiki page [1].
I'm curious about why a Referer header is always sent. Specifically for
"never", an empty string is sent. Why not just not send the header at
all? That's what is specified for @rel=noreferrer [2] for instance:
"If a user agent foll
14 matches
Mail list logo