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

"height: auto" overrides default height for audio elements, setting it to zero #819

Closed
DAreRodz opened this issue Jun 27, 2017 · 3 comments · Fixed by jgthms/minireset.css#15
Assignees

Comments

@DAreRodz
Copy link

Overview of the problem

I'm using Bulma version 0.3.0
My browser is: Google Chrome Version 59.0.3071.109 (Official Build) (64-bit)

Description

When the property height is set to auto for an audio element, the height of that element becomes zero while browser renders it with a default height, so that it appears cut or above other html elements. Removing "height: auto;" for audio tags solves the problem.

Steps to Reproduce

  1. Add an audio element inside a bulma content element.

Expected behavior

The audio element should have the height assigned by default (user agent stylesheet).

Actual behavior

The audio element appears cut or above other html elements.

Image 1:

screen shot 2017-06-27 at 12 14 07

Image 2:

screen shot 2017-06-27 at 13 30 42

@jgthms jgthms self-assigned this Jun 27, 2017
@jgthms
Copy link
Owner

jgthms commented Jun 27, 2017

Nice catch! Fixing now.

@jgthms jgthms closed this as completed in b8a7ab2 Jun 27, 2017
@dancollins84
Copy link

This issue does not appear to be fixed. The CSS still sets height: auto; for the audio tag. As I understand it, this is a problem because audio has no height property. For some reason, this doesn't make a difference in Firefox or Safari, but it breaks in Chrome.

@mcade
Copy link

mcade commented Dec 7, 2018

Are you going to merge this fix anytime soon @jgthms ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants