-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YouTube iframe code gets improperly escaped in rich text mode? #701
Comments
Hey @jywarren @TildaDares , is this issue still open, I want to work on it, |
Hi @RaviAnand111, yeah you can work on this. Thanks! |
2022-01-05.17-45-21.mp4Hey everyone @jywarren @TildaDares , I have found this, please share your views on it. |
If the video is not working, then this is the link of video on my drive. |
@RaviAnand111 I think the problem is the line break that is added to the |
oh great, I will try to recreate this and find a way to how to remove line breaks, |
so what I think is there is no problem with the editor and the youtube embed tool, |
@RaviAnand111 I tried using this SO answer to remove the line breaks but that removes the @jywarren is there a way to remove the line breaks before parsing to markdown?
|
Someone in the plots2 project (publiclab/plots2#9164) pasted this in, presumably in rich text mode, and the page broke - the iframe code seemed to get malformed and then the rest of the page wouldn't render.
I was able to paste it in "markdown" mode, not "rich text" and i wonder if that made it work.
I think @17sushmita's note that
allowfullscreen
becameallowfullscreen\=""
when in the rich text mode seems very likely to be our rich text editor code trying to "fix" that parameter but in fact breaking it.Let's try to reproduce this by pasting the above into the rich text mode editor and seeing if it causes a page cutoff or rendering problem?
If not, it could somehow relate to the action of publishing it after pasting in rich text mode in which case we could move back to the
plots2
project to investigate further.Thanks, all!!!
The text was updated successfully, but these errors were encountered: