| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
willchan pointed out that while idling, the chrome browser process can take up
to 25% CPU time on one of our Z600s, which is ridiculous. There's a lot of
causes here, but the first one I'm focusing on is how slow our tabstrip
rendering code is. Previously, each frame we stuffed bitmaps across the X11
connection instead of using cairo primitives for serverside accelerated
drawing.
This patch changes the code in tab_renderer_gtk.h from skia rendering (with
manually composited bitmaps) to cairo rendering (which should be a set of
commands to the x server that should composite bitmaps already living
serverside).
From here we can:
- Look for other ways to minimize the amount of work in an expose event.
- Only redraw the dirty rectangles or otherwise minimize the expose area.
- Finally fix that theme rendering bug where dragging a tab along the tabstrip
doesn't update to reflect the new background.
BUG=100803
TEST=Manual testing looking for graphical regressions.
Review URL: http://codereview.chromium.org/8392011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107514 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Operate on string16's instead of std::string's.
- Handle surrogate pairs correctly.
- Add out parameters returning the accelerated char pos and span.
These changes are necessary for my upcoming change to use this function
in a new CanvasSkia text drawing implementation.
BUG=none
TEST=Additional test cases added to skia_util_unittest.c.
Review URL: http://codereview.chromium.org/8229010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105107 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=97131
TEST=ui_unittests links and runs with use_aura=1
Review URL: http://codereview.chromium.org/7977025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102131 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Thanks to Kristian Høgsberg (krh@bitplanet.net) who submited the Wayland API changes.
I've also updated the native_widget_wayland.* to match the current implementations.
BUG=
TEST=
Review URL: http://codereview.chromium.org/7862021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101198 0039d316-1c4b-4281-b951-d872f2087c98
|
|
Follow the I18N recommendations for BiDi text editing.
BUG=90426
TEST=--use-pure-views text editing
Review URL: http://codereview.chromium.org/7511029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99987 0039d316-1c4b-4281-b951-d872f2087c98
|