<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK][EFL] Make gtk & efl port use s same media controls code."
href="https://bugs.webkit.org/show_bug.cgi?id=153601#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK][EFL] Make gtk & efl port use s same media controls code."
href="https://bugs.webkit.org/show_bug.cgi?id=153601">bug 153601</a>
from <span class="vcard"><a class="email" href="mailto:calvaris@igalia.com" title="Xabier RodrÃguez Calvar <calvaris@igalia.com>"> <span class="fn">Xabier RodrÃguez Calvar</span></a>
</span></b>
<pre>Answering the comment in <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GStreamer] built-in media player doesn't update"
href="show_bug.cgi?id=151816">bug 151816</a>.
(In reply to <a href="show_bug.cgi?id=153601#c28">comment #28</a>)
<span class="quote">> Basically I think the way is that we go. EFL had owned media control theme.
> But it was very poor quality controls. That's why we have used Apple's base
> media control themes. If EFL is continue to use base theme without GTK
> dependency when merging base + GTK+, I don't have any reason to object this
> plan.</span >
If you don't have issues now, you shouldn't have them after the merge. The only issues might be some icons or things like that, that can be easily solved with CSS or theming.
Anyway, the way to go, IMHO, would be to make the merge directly into, mediaControlsGTK, make GTK+ use only that file instead of Base+GTK and once that is ready, we can rename that into Base and polish any details in EFL. That would allow working only in one port until everything is ready.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>