| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
For context see this thread:
https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/RMcVNGjB4II
TBR=thakis,pkasting,jam
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146163 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the need for some Windows plumbing in
SingletonHwnd and fixes an issue where a WndProc
message would be getting sent after the Singleton
destruction, which was being triggered in ui_tests.
WindowImpl is robust against the above issue because
it stores a pointer to itself in the window user data
and clears it when it is destroyed.
BUG=105550
TEST=Running ui_tests with use_canvas_skia=1 on Windows shouldn't crash.
Review URL: https://chromiumcodereview.appspot.com/9965082
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130448 0039d316-1c4b-4281-b951-d872f2087c98
|
|
BUG=113184, 105550
TEST=Build Chrome Windows with gyp flag use_canvas_skia_skia=1. Open Chrome and observe text rendering in the tab strip, bookmarks bar, etc. Change Windows ClearType settings while Chrome is running. Text rendering should be updated appropriately.
Review URL: http://codereview.chromium.org/9370026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122514 0039d316-1c4b-4281-b951-d872f2087c98
|