Closed magreenblatt closed 12 years ago
Original comment by Dmitry Azaraev (Bitbucket: Mystic Artifact).
Comment 1. originally posted by fddima on 2012-05-28T11:09:01.000Z:
In addition to this issue - it will be cool have option to enabling/disabling prerender.
Original comment by Mark Johnston (Bitbucket: Mark Johnston).
Comment 2. originally posted by custa1200 on 2012-05-29T00:29:47.000Z:
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 Dmitry Azaraev (Bitbucket: Mystic Artifact).
Comment 3. originally posted by fddima on 2012-05-29T11:09:28.000Z:
Oh yes, you are right - prerendering is triggered by elements manually.
Original comment by Dmitry Azaraev (Bitbucket: Mystic Artifact).
Comment 4. originally posted by fddima on 2012-05-29T11:15:05.000Z:
UPDATE: To test prerendering is better to use http://prerender-test.appspot.com/ . Currently loading of this url cause crash in cefclient.
Comment 5. originally posted by magreenblatt on 2012-05-29T17:24:49.000Z:
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 Dmitry Azaraev (Bitbucket: Mystic Artifact).
Comment 6. originally posted by fddima on 2012-05-29T19:38:13.000Z:
Great, thanks!
PS: I think that stub it is enough. At least at this moment.
Comment 7. originally posted by magreenblatt on 2012-05-30T20:36:12.000Z:
Same problem with CEF1 trunk fixed in revision 657.
Original report by Dmitry Azaraev (Bitbucket: Mystic Artifact).
Original issue 608 created by fddima on 2012-05-28T11:00:29.000Z:
Reproduce problem, using CEF3/651:
Of course this pages opened normally in Chrome (21.0.1145.0 dev-m).
Sorry, can't obtain textual callstack (it is not writes in any file?), so see attached screenshot. Selected line with assert fails.