On Mon, 9 Apr 2012, Boris Zbarsky wrote:
On 4/9/12 2:16 PM, Gavin Peters (蓋文彼德斯) wrote:
However, this is strikingly similar to two other cases: when alink
rel=stylesheet ... element is removed from the document, in WebKit, we
remove the stylesheet from the document, although this isn't
On Mon, Apr 9, 2012 at 2:36 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 4/9/12 2:16 PM, Gavin Peters (蓋文彼德斯) wrote:
However, this is strikingly similar to two other cases: when alink
rel=stylesheet ... element is removed from the document, in WebKit, we
remove the stylesheet from the
Hi whatwg!
Since sending the below message, I've spent some time thinking about how to
handle the two cases I described in my initial posting, timeouts and load
events, and I think that both can be handled inside of the existing markup
framework on link rel=prerender... elements.
Also, I forgot
On 4/9/12 2:16 PM, Gavin Peters (蓋文彼德斯) wrote:
However, this is strikingly similar to two other cases: when alink
rel=stylesheet ... element is removed from the document, in WebKit, we
remove the stylesheet from the document, although this isn't explicitly
specified in 4.12.5.11,
We're having great luck in Chrome with link rel=prerender href=foo. If
that element with that rel attribute is in your document, Chrome launches a
hidden tab that we swap in and stitch into history if the user navigates
there. Navigation is as quick as switching tabs, you either join an
On Wed, 14 Mar 2012 15:35:14 -, Gavin Peters (蓋文彼德斯)
gav...@chromium.org wrote:
We're having great luck in Chrome with link rel=prerender href=foo. If
Does link rel=next href=doc2 not trigger this feature?
On 14 March 2012 14:40, Bjartur Thorlacius svartma...@gmail.com wrote:
On Wed, 14 Mar 2012 15:35:14 -, Gavin Peters (蓋文彼德斯)
gav...@chromium.org wrote:
We're having great luck in Chrome with link rel=prerender href=foo. If
Does link rel=next href=doc2 not trigger this feature?
No,
