Closed Bug 672037 Opened 13 years ago Closed 11 years ago

Audio element with small CSS height rule can resize itself, with usability side effects

Categories

(Toolkit :: Video/Audio Controls, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: WeirdAl, Unassigned)

References

Details

(Keywords: qawanted, testcase)

Attachments

(2 files)

I have an audio element with the CSS property height: 30px.  This is so that I show the controls only.  

When I click on the horizontal scale in the middle, it suddenly assumes a height more than twice that, and jumps out of the 30px height entirely.

Furthermore, clicking on the newly positioned scale does nothing, and clicks are only accepted within the original 30px box.

Test files coming momentarily.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a2) Gecko/20110716 Firefox/7.0a2
Attached file HTML test file
Steps to reproduce:
(1) Load attachment 546320 [details]
(2) Click the "play" button, and let it run for a few seconds.
(3) Click the "pause" button.
(4) Click in the center of the horizontal scale.

Expected results:
Audio visual features stay within the blue border box.

Actual results:
Audio visual features fall below the blue border box, and audio cannot be restarted or "scrolled in time" by clicking anywhere (either in blue box or on visual features).

Note that this testcase actually worked a little better locally (clicking inside blue box could restart audio) than it does hosted from Bugzilla.

I do not believe this is a regression - FF5 stock build had the same bug.
Keywords: testcase
Component: DOM: Core & HTML → Video/Audio Controls
Product: Core → Toolkit
QA Contact: general → video.audio
It the inverse problem, in my case, after reproducing using the step provided in comment 3 :
- The controls are no more responsive to clicks, but the time was still updating in the scrubber and in the progress bar.
- The controls are entirely below the blue box.
- The element width is lower.
Depends on: 619421
So can this bug now be marked as resolved? I can't reproduce it using current Firefox.
i've used to suffer from this bug but i can't reproduce it anymore (Firefox/Linux 64 bits)
let's assume it's fixed by bug 619421 as comment 6 states
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: