Bug 57620 – Layout issue with full screen view of a live video

• Component: Media
• Status: UNCONFIRMED

[Arnauld de La Grandiere]

Created attachment 87848 [details]
showcase of the full screen video player issue

Steps to reproduce :

- go to http://www.nonoche.com/webtv/index.html
- click on one of the icons and wait for a live video stream to start
- click on the full screen icon of the video

the "Live Broadcast" label in the full screen video controller is overlaid by the sound volume widget (see attachment)

[Jer Noble]

Looks like i missed one of the shadow elements.  This should be an easy fix: it will involve changing the css for the status field in fullscreenQuickTime.css.

[yevseytsev]

Tried to reproduce this bug using the link provided, but nothing works when you go there. After going through the logs I found out the file mentioned by Jer that he/she wanted to edit in order to fix a bug:

2011-06-15  Jer Noble  <[e-mail]>

        Reviewed by Timothy Hatcher.

        Full-screen live streams have status text in wrong location
        https://bugs.webkit.org/show_bug.cgi?id=62733

        Fix a misspelling in the user-agent stylesheet for full-screen mode.

        * css/fullscreenQuickTime.css:
        (video:-webkit-full-screen::-webkit-media-controls-status-display):

2011-06-14  Jer Noble  <[e-mail]>

        Reviewed by Eric Carlson.

        (AVFoundation) Apple event video appears as live stream and is not seekable
        https://bugs.webkit.org/show_bug.cgi?id=62694

        No new tests; There are no media-player port specific tests yet.

        Work around a bug in apple.com live stream javascript controller library.  When an AVAsset returns an indefinite time
        for its duration, return 0 if the asset has no tracks, and infinity otherwise.  This keeps the apple.com controller 
        from identifying the stored stream as a live stream.

        * platform/graphics/avfoundation/MediaPlayerPrivateAVFoundationObjC.mm:
        (WebCore::MediaPlayerPrivateAVFoundationObjC::platformDuration):

Surprisingly this fixes was referencing a very similar bugs that was resolved and fixed
https://bugs.webkit.org/show_bug.cgi?id=62733
https://bugs.webkit.org/show_bug.cgi?id=62694