-
Notifications
You must be signed in to change notification settings - Fork 58
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
Enable Cover Block for Production #2034
Conversation
Hey @iamthomasbishop ! Here's the Cover Block build for you to test when you have some time, you can check these test cases of the functionality we have so far.
Thanks!! |
Great work overall! Most of the test scenarios worked as expected, I just have a few bits of feedback:
Head’s up: We’ll soon be able to utilize the color picker in mobile, so perhaps we can consider adding that in the next iteration of the cover block via block settings? 😄 // cc @lukewalczak |
Thanks for testing!
By semi-transparent, you mean using the alpha values? If it is that, I tried changing those values and it works so maybe it's something else? WebMobile
Not really 😅these settings are per block basis so we'd need to modify each block that has support for color / background styles. In this case, we'd need to update the
Yay! Can't wait to have that in the next iterations of Cover. |
Correct, I did mean alpha, sorry I didn't explain very clearly. Here's what I'm seeing. If you have a background-image and a gradient overlay (at any opacity), the overlay becomes 100% opaque regardless of what the opacity setting is set to. For example, here is the same block on web vs. mobile: Web Mobile Hope that helps clarify.
Ah, of course, that makes sense, we can tackle that separately.
🙌 🎉 |
Ahh I get it now 😅so we haven't added that functionality to set a gradient as an overlay, there's an open issue but work on it hasn't started yet. That's why you're only seeing the gradient as a background. Maybe @pinarol can tell us about the priority of that one. |
@geriux Actually that open issue is for making the gradient settings available in mobile. I was already assuming that we are rendering the alpha level of gradient overlay correctly in this iteration. Can we make that happen? I can help where needed. It would look like a bug as is. |
Ah ok. I understand not giving the user the ability to set the gradient as an overlay from the mobile editor because we aren't quite ready in terms of color picking/customization, but we should definitely support gradients over the top of images at any user-configured opacity value. It might not be the highest priority thing, but it was confusing to me. It could be a fairly rare use case, so perhaps it's not the highest priority, just wanted to mention it. |
Yeah we are not supporting it yet (as an overlay) since the work done was just to add them as backgrounds, I guess it was just a misunderstanding of the task 😅 We can make it happen of course, I was already reviewing what we would need to change so I can work on that tomorrow and put it up for review =) |
Technically i was assuming the background and overlay would correspond to the same thing. I wasn’t expecting we’d need to do a separate implementation for overlay. If we put the image at the bottom and put the gradient layer on top of it, it should act as a background when there’s no image. But I might be missing something. |
That's what I was also thinking, @pinarol. I figured the gradient would be a layer with a higher z-index than the background image. This would make both optional and allow them to work in tandem. |
Yeah, there's no much change technically. I just thought the issue was just for that hence me reviewing the PR and not requesting the overlay. But don't worry I'll have it done by today =) |
Hey all 👋 changes are done. This is how it's looking now: I've made a new build for you to test here. Thanks for the feedback! |
Wow that was quick 👏 Thank you very much @geriux ! |
@geriux Running the app through metro I'm getting a red screen for one of the block configurations I have set up. This seems to only happen on one of my blocks so far. Here are the settings I used:
Here's the generated block code:
|
Walking through those settings it seems like Focal point seems to be causing the issue |
Thanks Chip! I'll check it out |
@chipsnyder So I can't seem to be able to reproduce this, can you please try the builds I made? Thanks! |
Using the builds iOS worked fine but I got the same error in Android on a Pixel 3a running API 29 if that becomes important |
Awesome work! Looks great. I haven't had a chance to test a build yet, but I will check for an update. |
Had a chance to check out the test build — looks great @geriux! 👍 |
@chipsnyder I encountered the same or similar validation red screen at one point, on Android Pixel 3a as well, but after reinstalling the app, I couldn't reproduce it, and haven't seen it since - just wanted to note this here, to confirm I also encountered it. |
Hi @geriux 👋 Very nice work on this block. This is looking really nice! I tested out via the test cases, and it's mostly working, with a few issues (TC005 - Android, TC006):
For this test case, on iOS everything worked as expected (no sound 🔇),
Update: I tested this again, and this commit seems to have fixed the issue. Nice work! 👍
|
Step 4 | Step 11 | Step 14 |
---|---|---|
I'm not certain whether both steps 3 and 4 are necessary to reproduce this, but I did not encounter the issue when I tried to reproduce it omitting both of those steps.
Hey @mkevins ! Thanks for testing and the feedback 😃
I was trying this one and I can't reproduce it. Were you testing the build from the WordPress Android PR? Which device were you using? Did it happen in different scenarios? Adding the block from mobile, opening a post? |
Regarding this issue, it is solved now =D thanks for spotting that! Here are the new builds.
|
Tested on iOS with this build I was able to see my block without the focal point error once but after that I got the error parsing block message. I see you opened an issue for that though. Going through the test cases it looks pretty solid. I only had one issue/question: |
This occurred in two different scenarios:
I encountered this on Android Pixel 3a (real device), via WordPress-Android |
Hey @chipsnyder thanks for testing again!
What do you mean with a gray screen? Missing thumbnail? Was this video already in your WordPress media library? Was this on Android? iOS? both? |
Hey @mkevins thanks for testing again!
Since we are enabling this for production, could you please test the peril build instead of running metro on develop? Also discussed this with @pinarol if that still happens to you (video with sound) we can keep iterating on it after releasing. Video usage is not that high and it wouldn't be a blocker to release the Cover block. 😃 Same as the focal point issue cc @chipsnyder. Thank you both for testing this! 🙌 |
Hmm looks like it's taking it a bit to process the video/thumbnail. But yeah definitely not related to the block itself. |
I assumed it was probably something with my videos. Thanks for confirming :) I'll mess with it and open a different issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested on iOS and Android. Looks good!
I ran into one issue with Video preventing me from testing that. However, it appears to be an issue with the videos and not the block itself.
I downloaded the apk and tried with my Huawei p20 lite, Android 9.0. I was able to successfully add a video background with a device recorded video. And the sound was muted as expected. The video player library we have on react native has some intermittent issues about inline video playing and video previews. That was one of the reasons we wanted to defer the playing to browser/external app on Android for Video block. Cover block video backgrounds are quite rare, thus I am not that worried about it. Even if there's something to fix, it needs to be done in library level so let's try to report if we can detect sth reproducible. We can also try updating the lib, we are using 4.4.1 and 4.4.5 seems available, although, couldn't see anything related in the release logs. |
Awesome thank you for testing this!
This is great background thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we are enabling this for production, could you please test the peril build instead of running metro on develop?
Certainly! For whatever reason, at the time of testing, the apk wasn't available for Android, but I did test the peril build for iOS.
I just retested with this apk, and the Video is now muted 🔇 🎉 .
I also tested this again, and this commit seems to have fixed the aspect ratio issue.
So, both TC005 and TC006 seem to be resolved now. Nice work @geriux ! LGTM!
Yay! Thank you so much for testing!! |
Fixes #2005 and also fixes #2052
Gutenberg PR
-> WordPress/gutenberg#20992To test check Gutenberg PR description
PR submission checklist:
RELEASE-NOTES.txt
if necessary.