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
There are couple of items that can be improved with Winamp block:
With Winamp block in admin, when I click on "Preview Player" then the player always sticks to the top making it really hard for the first time user to get back to normal player mode until the user refreshes the page or try scrolling as the player it sticked at the top scrolling helps to show the option and then we can change it to normal player mode from preview. The editorial experience around this needs some improvement See screenshot:
The player in the frontend looks good. However, I feel there are couple of things that might need improvement:
The player buttons looks disabled irrespective of it being enabled/disabled
The player can be moved around on the page overlapping the content but that leaves a space where it was originally placed. So, wondering if moving around of player is a feature then can we make the whitespace to be moved around along with it? 💭
Note: I think all the items I mentioned should not be a problem. But, just wanted to add my experience being a new user.
Steps to Reproduce
Add a Winamp block
Add some other paragraph block with some content
Click on "Preview" to preview the Winamp block
You will see there is no way to go back to the editing of Winamp block
Screenshots, screen recording, code snippet
No response
Environment information
No response
WordPress information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
There are couple of items that can be improved with Winamp block:
Note: I think all the items I mentioned should not be a problem. But, just wanted to add my experience being a new user.
Steps to Reproduce
Screenshots, screen recording, code snippet
No response
Environment information
No response
WordPress information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: