Bug 136644 – Separate the Apple media controls module from other ports

• Status: RESOLVED
• Resolution: FIXED
• Component: Media

[Dean Jackson]

Currently, mediaControlsApple is acting as the base class for all ports that use JS-based controls. It's nice that we're trying to consolidate all behaviour into one place, but that one place should not be an Apple-specific controller.

For now, make a Base.js that is identical to the Apple.js, and have the EFL and GTK ports use that. Over time we'll probably change Apple.js to use the same base.

[Dean Jackson]

Lots of discussion in 131951

[Dean Jackson]

https://bugs.webkit.org/show_bug.cgi?id=131951

[Dean Jackson]

rdar://problem/18270969

[Dean Jackson]

Created attachment 237812 [details]
Patch

[Dean Jackson]

Letting EWS check the ports I can't build.

[Dean Jackson]

EFL EWS seems to be stuck. Committing for now.

[Dean Jackson]

Committed r173401: <http://trac.webkit.org/changeset/173401>

[Xabier Rodríguez Calvar]

(In reply to comment #0)
> Currently, mediaControlsApple is acting as the base class for all ports that use JS-based controls. It's nice that we're trying to consolidate all behaviour into one place, but that one place should not be an Apple-specific controller.
> 
> For now, make a Base.js that is identical to the Apple.js, and have the EFL and GTK ports use that. Over time we'll probably change Apple.js to use the same base.

For me it would be more credible if you had based the Apple controls already on Base, otherwise the discussion on bug 131951 is completely disregarded.

[Dean Jackson]

(In reply to comment #8)
 
> For me it would be more credible if you had based the Apple controls already on Base, otherwise the discussion on bug 131951 is completely disregarded.

I understand your point, although this stuff is really supposed to be platform specific. The part that is really the base of the implementation is the HTMLMediaElement and the MediaControlsHost.

For example, we might want to replicate the way scrubbing works on iOS, where vertical position implies a scrubbing speed. That's not a stylistic thing - it's behaviour that we'd have to implement. It's quite hard to do that for platforms you don't have access to.

We're already sharing base functionality. All this change did was move it up the stack a bit.