#6 Render sometimes fails in Chrome

Chris Cole

(Reported in discussions, but not verified)

Thanks for your reply. I actually ran into some trouble with Chrome, as it would try to render the SafeFrame before the HTML5 init check was done. Got it sorted by adding an "HTML5 check done" flag to _check_html5_init() and waiting for it to be set before proceeding with the rendering. With this small addition, everything's fine so far.


  • Viktor

    Viktor - 2013-11-21

    I just noticed this ticket. To clarify, the rendering problems in Chrome started occurring only after I removed the waiting for the DOM to be ready, which is why I had to add the extra "HTML5 check done" check.

    With the DOM wait present (unmodified SafeFrame code), the rendering works nicely.

  • Chris Cole

    Chris Cole - 2015-01-23
    • status: open --> closed
    • assigned_to: Chris Cole

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks