Skip to content
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

Clicking on an embedded video block should select it #11885

Closed
redknite opened this issue Nov 14, 2018 · 5 comments
Closed

Clicking on an embedded video block should select it #11885

redknite opened this issue Nov 14, 2018 · 5 comments
Labels
[Block] Embed Affects the Embed Block [Feature] Blocks Overall functionality of blocks [Priority] High Used to indicate top priority items that need quick attention [Type] Bug An existing feature does not function as intended
Milestone

Comments

@redknite
Copy link

redknite commented Nov 14, 2018

I can edit the vimeo block fine on chrome by clicking on it, but when I'm in firefox clicking on the video block only starts and stops the video. Block section on right continues to show "no block selected" and toolbox that should appear over the box does not show up.

Additionally in my console on firefox I get theses issues noted: (I'm only using the "welcome to gutenburg" post and no changes have been made/saved.)

InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable player.js:2

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://fresnel.vimeocdn.com/add/player-stats?session-id=eb87b4def6a15e680e27deb06eb079f4ba309e751542235378&es=1. (Reason: CORS request did not succeed).[Learn More]

in chrome, when I try to view this block in html, I get this noted in my console:

JQMIGRATE: Migrate is installed, version 1.4.1
index.js?ver=1542233778:19 [Violation] Avoid using document.write().
value @ index.js?ver=1542233778:19
value @ index.js?ver=1542233778:19
jc @ react-dom.min.82e21c65.js:134
gc @ react-dom.min.82e21c65.js:127
vb @ react-dom.min.82e21c65.js:126
ub @ react-dom.min.82e21c65.js:126
wg @ react-dom.min.82e21c65.js:137
Ze @ react-dom.min.82e21c65.js:41
player.js:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
(anonymous) @ player.js:2
h.addEvent @ player.js:2
Tu.addEvent @ player.js:2
o @ player.js:2
h.on @ player.js:2
be @ player.js:2
Jf @ player.js:2
(anonymous) @ player.js:2
initializationHandler @ player.js:2
(anonymous) @ player.js:2
player.js:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
(anonymous) @ player.js:2
h.addEvent @ player.js:2
Tu.addEvent @ player.js:2
o @ player.js:2
h.on @ player.js:2
(anonymous) @ player.js:2
th @ player.js:2
(anonymous) @ player.js:2
initializationHandler @ player.js:2
(anonymous) @ player.js:2
player.js:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

@designsimply designsimply added the Needs Testing Needs further testing to be confirmed. label Nov 14, 2018
@designsimply
Copy link
Member

Tested and confirmed with WordPress 4.9.8 and Gutenberg 4.3 using Chrome 70.0.3538.77 and Firefox 63.0.1 on macOS 10.13.6 that clicking on a Vimeo embed in the editor does not result in the block being activated and so the caption and block toolbar areas do not show up as expected. I found that if I click on the very very far right side, I can get it to work in case that's helpful debugging info. (2m1s)

screen shot 2018-11-14 at 4 49 38 pm
Seen at http://alittletestblog.com/wp-admin/post.php?post=16232&action=edit running WordPress 4.9.8 and Gutenberg 4.3 using Firefox 63.0.1 on macOS 10.13.6.

I did not see any of the same console errors noted though. @redknite may I ask you to note versions for your OS and the browsers you tested with for reference and which theme you are using if you're able?

@designsimply designsimply added [Type] Bug An existing feature does not function as intended Browser Issues Issues or PRs that are related to browser specific problems [Block] Video Affects the Video Block and removed Needs Testing Needs further testing to be confirmed. labels Nov 14, 2018
@redknite
Copy link
Author

redknite commented Nov 15, 2018

@designsimply Thanks for the quick reply! I'm on windows 7 running firefox 63.0.1 (64-bit) and Chrome Version 70.0.3538.102 (Official Build) (64-bit). Wordpress is on 4.9.8 and I'm on twentyfifteen 2.0 theme.

@designsimply
Copy link
Member

Thanks! The important issue here is that when you click on an embedded video, the toolbar does not appear and I can confirm this problem. I believe the expectation is that the first click on an embedded video should select it (at which point the block toolbar should appear).

I was also curious about the console errors and so I've tested again and here's what I found:

I tested with Firefox 63. on Win7 and now I see the CORS message, however, it is a warning not an error—which may mean it's not significant—and I was unable to see the InvalidStateError on Windows.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://fresnel.vimeocdn.com/add/player-stats?session-id=123ea873be602ee6a0fa58a26b90edb4a2876a4e1542765775. (Reason: CORS request did not succeed).[Learn More]

bs_win7_firefox_63 0
Seen at http://alittletestblog.com/wp-admin/post.php?post=16232&action=edit using Firefox 63 on Windows 7 with WordPress 4.9.8 and Gutenberg 4.5.

I was able to see the InvalidStateError on macOS after updating the plugin from 4.4 to 4.5 and then viewing the Gutenberg > Demo:

InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable
player.js:2

screen shot 2018-11-20 at 7 16 22 pm
Seen at https://tan-otter.jurassic.ninja/wp-admin/post-new.php?gutenberg-demo running WordPress 4.9.8 and Gutenberg 4.5 using Firefox 63.0.1 on macOS 10.13.6.

screen shot 2018-11-20 at 7 22 17 pm
Seen at https://tan-otter.jurassic.ninja/wp-admin/post-new.php?gutenberg-demo running WordPress 4.9.8 and Gutenberg 4.5 using Firefox 63.0.1 on macOS 10.13.6.

Note: the InvalideStateError seems to be an error coming from Vimeo's player directly (I think). I see that error both in the editor view and on the front end and it doesn't seem to have any effect on whether or not I can play the video.

I am not sure whether the console messages are important to the problem in this case but it is still good to explore them!

@designsimply designsimply changed the title can't edit vimeo on firefox Clicking on an embedded video block should select it Nov 21, 2018
@designsimply designsimply added [Block] Embed Affects the Embed Block and removed Browser Issues Issues or PRs that are related to browser specific problems [Block] Video Affects the Video Block labels Nov 21, 2018
@designsimply
Copy link
Member

designsimply commented Nov 21, 2018

I noticed this happens with other video embeds as well.

Video: 1m58s
Tested with WordPress 4.9.8 and Gutenberg 53e4c40bd (4.5.1+) using Firefox 63.0.1 on macOS 10.13.6.

@designsimply designsimply added the [Priority] High Used to indicate top priority items that need quick attention label Dec 4, 2018
@designsimply designsimply added the [Feature] Blocks Overall functionality of blocks label Dec 5, 2018
@jasmussen
Copy link
Contributor

This has been discussed in the past, and believed fixed. But it's clearly an issue again. I have reopened #483, which is the best place to discuss this, and I'm going to close this one in favor of that to keep the discussion there. Thank you for resurfacing the issue, let's get it fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Embed Affects the Embed Block [Feature] Blocks Overall functionality of blocks [Priority] High Used to indicate top priority items that need quick attention [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

3 participants