Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Ivan Paramonau

    (@ivanp)

    Thank you for reporting. This is possible because we override your setting with iframe=1 for the Gutenberg editor.

    We’ll include a handler with our next update. Cannot share specific plans yet though.

    Thread Starter gebeer

    (@gebeer)

    Thank you for the quick reply. We will wait for the next update then.
    Cheers

    Plugin Author Ivan Paramonau

    (@ivanp)

    I am revisiting this bug and noticed that I actually could have helped you sooner.

    Our API parameters, for a while now, mention it separately – &iframe=1&card=1 – instead of the combined &iframe=card.

    So if you configure this way, it should work consistently on the front-end and in Gutenberg.

    (notwithstanding, we’re still going to fix the problem with &iframe=card being ignored in Gutengerg)

    Thread Starter gebeer

    (@gebeer)

    @ivanp Thank you for thhat hint. After updating the plugin settings to read iframe=1&card=1 I get consistent behaviour.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Inconsistent behaviour for different Twitter types in editor preview’ is closed to new replies.