Closed
Bug 1340479
Opened 8 years ago
Closed 8 years ago
Media control panel elements don't meet the distances given in the specifications document
Categories
(Toolkit :: Video/Audio Controls, defect)
Toolkit
Video/Audio Controls
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox51 | --- | unaffected |
firefox52 | --- | unaffected |
firefox53 | --- | affected |
firefox54 | --- | affected |
People
(Reporter: JuliaC, Unassigned)
References
Details
[Affected versions]:
- Windows 10 x64
- Ubuntu 14.04 x64
- Mac OS X 10.12
[Affected platforms]:
- Latest Aurora 53.0a2 (2017-02-16)
- Latest Nightly 54.0a1 (2017-02-16)
[Steps to reproduce]:
1. Launch Firefox
2. Go to https://people-mozilla.org/~ralin/vtt/
3. Measure the distances between the media control panel elements and compare with the specs https://drive.google.com/file/d/0B4K8q1qWmtAvM3ZXVUlHRkdRVVU/view
[Expected result]:
- The media device elements meet the specs
[Actual result]:
- The media device elements meet the specs (see http://i.imgur.com/32oXdEf.png - default window size and http://i.imgur.com/sUSk2pO.png - small window size)
[Regression range]:
- The issue is not a regression, because it is reproducible since 53.0a1 (2016-11-19), when Visual refresh of media controls was implemented
Reporter | ||
Updated•8 years ago
|
Summary: Media control panel elements does not meet the distances given in the specifications document → Media control panel elements don't meet the distances given in the specifications document
Comment 1•8 years ago
|
||
Hi Lulia,
I don't think it's a right way to measure the distance, using Browser Toolbox to inspect box model would be more accurate.
At first visual design and I tried out a few breakpoints for responsiveness, but later we decided to control layout by javascript and shrunk the distance between controls as well. I'll find out the latest spec about this change.
set this bug as invalid as this layout is confirmed with visual design.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•