RESOLVED FIXED 131258
Honor System-Level User Preferences for Captions Display
https://bugs.webkit.org/show_bug.cgi?id=131258
Summary Honor System-Level User Preferences for Captions Display
Brent Fulgham
Reported 2014-04-04 21:15:06 PDT
WebKit doesn't properly honor the global user preferences for caption display in a few cases: 1. When a video starts playing, it should show captions if the user's preferences indicate a preference for caption display. 2. While a video is playing, captions should turn on/off as the user changes preferences. 3. Regardless of the user's preferences, if the user manually selects captions they should be displayed. In all cases, the result of the following JavaScript should reflect what's going on in the video playback: document.querySelector("video").webkitClosedCaptionsVisible
Attachments
Patch (3.06 KB, patch)
2014-04-04 21:24 PDT, Brent Fulgham
eric.carlson: review+
Brent Fulgham
Comment 1 2014-04-04 21:15:55 PDT
Brent Fulgham
Comment 2 2014-04-04 21:24:30 PDT
Brent Fulgham
Comment 3 2014-04-04 21:27:35 PDT
Comment on attachment 228653 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=228653&action=review > Source/WebCore/html/HTMLMediaElement.cpp:-3713 > - m_captionDisplayMode = displayMode; I needed to do this so that the "ForceOn" state was properly seen by system.
Brent Fulgham
Comment 4 2014-04-04 22:20:17 PDT
All tests (including uncommitted region tests) pass with this change.
Jon Lee
Comment 5 2014-04-05 14:22:45 PDT
(In reply to comment #4) > All tests (including uncommitted region tests) pass with this change. Additional test case, then?
Brent Fulgham
Comment 6 2014-04-05 20:04:36 PDT
(In reply to comment #5) > (In reply to comment #4) > > All tests (including uncommitted region tests) pass with this change. > > Additional test case, then? after looking at it, I realize it's just a local copy of one of the Opera tests. I'm trying to get the whole set of them turned on in an upcoming patch.
Brent Fulgham
Comment 7 2014-04-06 16:22:15 PDT
Note You need to log in before you can comment on or make changes to this bug.