Closed GoogleCodeExporter closed 9 years ago
In addition to this issue - it will be cool have option to enabling/disabling
prerender.
Original comment by fdd...@gmail.com
on 28 May 2012 at 11:09
I never thought about the fact that Chromium now does pre-rendering which is
something we would not want it to do in our line of business app. We would not
want any transactions to be run against our core system unnecessarily from a
linked page.
Original comment by custa1...@gmail.com
on 29 May 2012 at 12:29
Oh yes, you are right - prerendering is triggered by <link rel="prerender">
elements manually.
Original comment by fdd...@gmail.com
on 29 May 2012 at 11:09
UPDATE: To test prerendering is better to use
http://prerender-test.appspot.com/ . Currently loading of this url cause crash
in cefclient.
Original comment by fdd...@gmail.com
on 29 May 2012 at 11:15
Revision 652 fixes the crash by adding stub implementations for
WebKit::WebPrerenderingSupport and WebKit::WebPrerendererClient. Chromium's
prerendering implementation currently lives in chrome/renderer/prerender and
chrome/browser/prerender. I'm not aware of any plans currently for add
prerendering support to the Content API.
Original comment by magreenb...@gmail.com
on 29 May 2012 at 5:24
Great, thanks!
PS: I think that stub it is enough. At least at this moment.
Original comment by fdd...@gmail.com
on 29 May 2012 at 7:38
Same problem with CEF1 trunk fixed in revision 657.
Original comment by magreenb...@gmail.com
on 30 May 2012 at 8:36
Original issue reported on code.google.com by
fdd...@gmail.com
on 28 May 2012 at 11:00Attachments: