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

Improve layout for audio and video tags in whatsapp chats opened in browser #1842

Closed
gfd2020 opened this issue Aug 24, 2023 · 3 comments · Fixed by #1841
Closed

Improve layout for audio and video tags in whatsapp chats opened in browser #1842

gfd2020 opened this issue Aug 24, 2023 · 3 comments · Fixed by #1841

Comments

@gfd2020
Copy link
Collaborator

gfd2020 commented Aug 24, 2023

The audio and video controls may broken html layout on browser ( whatsapp html chats).

image

Repair suggestion below ( CSS ) - Tested on PR 1767:

video {
max-width:100%;
display: block;
}
audio {
max-width:100%;
width:550px;
display: block;
}

@wladimirleite
Copy link
Member

wladimirleite commented Aug 24, 2023

Thanks @gfd2020!

I added a <br> after audio/video titles (commit 8a7604f) and it seems to have a similar effect of display: block;.

I liked the wider audio control.
Do you want to create a PR yourself, or may I include this in PR #1841?

@gfd2020
Copy link
Collaborator Author

gfd2020 commented Aug 24, 2023

Thanks @gfd2020!

I added a <br> after audio/video titles (commit 8a7604f) and it seems to have a similar effect of display: block;.

I liked the wider audio control. Do you want to create a PR yourself, or may I include this in PR #1841?

Can you make the changes? Please?

@wladimirleite
Copy link
Member

Sure! Thank you once again!

@lfcnassif lfcnassif changed the title Broken layout for audio and video tags in whatsapp chats opened in browser Improve layout for audio and video tags in whatsapp chats opened in browser Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants