You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have users that expect to be able to embed things like Google Forms or Qualtrics Surveys via iframe. When doing so, the <iframe> markup is treated as a video embed and subsequently wrapped in the video embed markup.
To Reproduce
Steps to reproduce the behavior:
Using an editor that has code view, click the code view icon.
My users expect their <iframe ...></iframe> to be left alone, however I would argue that such an expectation is not yet defined, but probably should be, ie. there should be some way to signal to SunEditor that it must leave a given iframe alone.
I can think of two possible ways to handle this, (though I'm sure you have more and better ideas 😄 ):
Only create the wrapper markup when the actual SunEditor Video embed plugin is used. This is probably too drastic.
Create a special data-* attribute that can be used by "power users" to override the video wrapper, ie. <iframe data-se-video-embed="false" src="..."></iframe>
The text was updated successfully, but these errors were encountered:
Describe the bug
I have users that expect to be able to embed things like Google Forms or Qualtrics Surveys via iframe. When doing so, the
<iframe>
markup is treated as a video embed and subsequently wrapped in the video embed markup.To Reproduce
Steps to reproduce the behavior:
Expected behavior
My users expect their
<iframe ...></iframe>
to be left alone, however I would argue that such an expectation is not yet defined, but probably should be, ie. there should be some way to signal to SunEditor that it must leave a given iframe alone.I can think of two possible ways to handle this, (though I'm sure you have more and better ideas 😄 ):
data-*
attribute that can be used by "power users" to override the video wrapper, ie.<iframe data-se-video-embed="false" src="..."></iframe>
The text was updated successfully, but these errors were encountered: