<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Implement rendering frames timeline panel for GTK+ port"
href="https://bugs.webkit.org/show_bug.cgi?id=150392#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Implement rendering frames timeline panel for GTK+ port"
href="https://bugs.webkit.org/show_bug.cgi?id=150392">bug 150392</a>
from <span class="vcard"><a class="email" href="mailto:bburg@apple.com" title="Brian Burg <bburg@apple.com>"> <span class="fn">Brian Burg</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=150392#c0">comment #0</a>)
<span class="quote">> The mac implementation is based on RunLoopObserver, that only has
> an implementation based on CF. It's not currently possible to do the same
> with the glib main loop, so even if there's a proper platform abstraction of
> RunLoopObserver, we won't be able to provide a glib implementation. Maybe
> when persistent sources patch lands (see <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Add persistent GSource wrapper"
href="show_bug.cgi?id=138691">bug #138691</a>), we can provide a way
> to monitor our sources.</span >
If you could provide some rationale for why RunLoopObserver isn't a sufficient abstraction in <<a class="bz_bug_link
bz_status_NEW "
title="NEW - Provide a better RunLoopObserver platform abstraction"
href="show_bug.cgi?id=142748">https://bugs.webkit.org/show_bug.cgi?id=142748</a>>, that would be helpful in moving that discussion forward.</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>