Last Comment Bug 754874 - OMTC: Qt MessageLoop should use CurrentThread object for event dispatching
: OMTC: Qt MessageLoop should use CurrentThread object for event dispatching
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: IPC (show other bugs)
: unspecified
: x86 Linux
: -- normal (vote)
: mozilla16
Assigned To: Oleg Romashin (:romaxa)
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-14 09:03 PDT by Oleg Romashin (:romaxa)
Modified: 2012-06-09 19:49 PDT (History)
3 users (show)
dzbarsky: in‑testsuite-
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
Use Qthread::currentThread for dispatching chromium native events (1.46 KB, patch)
2012-05-14 09:03 PDT, Oleg Romashin (:romaxa)
doug.turner: review+
Details | Diff | Splinter Review

Description Oleg Romashin (:romaxa) 2012-05-14 09:03:04 PDT
Created attachment 623694 [details] [diff] [review]
Use Qthread::currentThread for dispatching chromium native events

As followup to the bug 750960, we should do the same in chromium loop
Comment 1 David Zbarsky (:dzbarsky) 2012-06-09 15:23:40 PDT
I didn't realize this until after I pushed, but you didn't have an author in your commit, so it ended up switching to me.  Sorry.

https://hg.mozilla.org/integration/mozilla-inbound/rev/b8a593d4e0e2
Comment 2 Ryan VanderMeulen [:RyanVM] 2012-06-09 19:49:40 PDT
https://hg.mozilla.org/mozilla-central/rev/b8a593d4e0e2

Note You need to log in before you can comment on or make changes to this bug.