Closed Bug 660352 Opened 14 years ago Closed 14 years ago

Controls do not hide when youtube.com HTML5 video is played fullscreen if mouse is over content

Categories

(Core :: Audio/Video, defect)

Product:
Core
Component:
Audio/Video
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: aceman, Unassigned)

References

(
URL
)

Details

(Whiteboard: [bugday-2011-05-27][chrome-parity][opera-parity]) 

1. activate HTMl5 mode on www.youtube.com/html5
2. go to http://www.youtube.com/watch?v=2klla_YJqew
3. click fullscreen, click play
4. have the mouse somewhere on the video, but not on the progress bar (the bottom red line)

Result:
The progress bar tries to fade out after several seconds of inactivity, but comes back instantly.

Expected result:
The progress bar should hide and stay away when mouse is inactive.

Opera 11 and Chrome 12 work fine.
Tested and confirmed also by other user on Firefox 4.0 up to 7.0.
Summary: progress bar does not hide when youtube.com html5 webm is played fullscreen → progress bar does not hide when youtube.com HTML5 webm video is played fullscreen
Confirmed: Tested Chromium 13 and no issues. All Firefox 4 to 7 in win 7 behaves like bug says.
It works as expected if the mouse is over the browser chrome or outside the window entirely.
Summary: progress bar does not hide when youtube.com HTML5 webm video is played fullscreen → Controls do not hide when youtube.com HTML5 video is played fullscreen if mouse is over content
Youtube has fixed this problem. No issues anymore. This bug should marked as fixed/invalid now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Was it a bug in youtube or have they just worked around a Firefox problem?
I think it was in youtube. Who knows;) Google/youtube bug commenting is very frustrating. I didn't get any mail or something that someone actually checked my bug reporting.
Marking VERIFIED WORKSFORME using the 20110614 Nightly.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.