We seem to be having an issue where visible YouTube embeds will cause the html text editor of content blocks to lock up. If the embed is hidden through CSS, and is thus invisible in the regular text editor, the editor works normally, no problem. It's only when the embeds are visible, and it also seems to only occur when switching from the regular text editor to the html one.
We're using version 7.0.
Any thoughts on what might be causing this?
The issue doesn't occur when working within the Design window of the text editor. In that scenario, yes, the editor works fine. The issue pops up when switching from Design to HTML. When switching to HTML, the text field will lock up; it's not possible to put the cursor into the field or type anything.
The iframe is what triggers the content block to lock up, though. Otherwise, without the iframe inside the content block, yes, the content block functions normally. Let me reiterate the problem:
1. I put the content block on the page.
2. I go to the HTML view on the content block. I paste the YouTube iframe's html into the text editor.
3. I switch to Design view. The YouTube video player loads in the text editor. It looks fine. It works fine. No problems there. If I stay in Design view, I can add text around the video however I see fit. Everything works fine.
4. When I switch back to HTML view, and I try to insert my cursor into the text editor, I can't. I can't select any of the HTML text, either. I can hit save. I can go back to Design view. Basically, I can use any of the buttons, but I can't get my cursor inside the text editor.
Does this make more sense? If not, I can try to make a video that illustrates the problem.
Here is the screencast.
Any YouTube video will cause the problem. The ones I used in the screencast were ones that I chose randomly, and with those, the problem still happened. Here is one of the videos I used in the screencast.
We can probably try to create a new project, but we were hoping that someone could try to reproduce the problem on their end first.
Oh, yes, now that you mention a possible browser issue, I've checked and it happens with only Google Chrome. I guess a recent update for the browser might have created the bug.
Thanks for the help!