Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Mark (a11n)

    (@thingalon)

    Hey, thanks for trying Jetpack Boost out!

    Jetpack Boost uses an invisible iframe to generate Critical CSS for your site. That iframe is configured with strict sandboxing rules for a few reasons; to help protect your admin dashboard from unexpected script execution, to ensure that scripts for tracking page views aren’t triggered (so we don’t mess up your stats), and to ensure that the Critical CSS we generate reflects the initial page-load content without external scripts affecting the layout.

    Unfortunately, browsers tend to log those messages to the console to let developers know that resources are being blocked by the iframe’s sandboxing rules.

    They aren’t a signal that anything has gone wrong; they just indicate that your browser is correctly enforcing the iframe sandboxing rules.

    Thread Starter Mike Zielonka

    (@mikezielonka)

    It’s likely due to my wordpress.com not being connected to the sites since it uses my customers’ account.

    Thread Starter Mike Zielonka

    (@mikezielonka)

    Yep!

    Just wasn’t sure if you guys were aware. Could throw off a non-technical user!

    Mike

    Plugin Contributor Mark (a11n)

    (@thingalon)

    Oh! I apologize, Mike – I misunderstood the context of the error you were describing.

    I’ve tracked down the issue, and we will release a fix in the next version of Jetpack Boost (soon!)

    Thanks for the report!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘iframe error’ is closed to new replies.