This isn't just about message priorities. It is also about thread
priorities. There is no point in having the renderer produces new images of
the page if the browser process hasn't put them on the screen yet.
-Darin
On Mon, Apr 13, 2009 at 11:28 AM, Adam Langley <a...@chromium.org> wrote:
>
> On Mon, Apr 13, 2009 at 11:12 AM, Peter Kasting <pkast...@google.com>
> wrote:
> > Perhaps not "safe", but "not worse".
>
> It's not that don't want to deal with this right now, it's that I
> believe that the current behaviour is correct on Linux. I've reread
> your patch and email and I haven't understood any arguments about why
> there's a problem. (I get that there might be something about the
> priority of Windows WM_PAINT messages that causes an issue, but that
> obviously doesn't apply with X.)
>
>
> AGL
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
