summaryrefslogtreecommitdiffstats
path: root/chrome/browser/views
diff options
context:
space:
mode:
authormaf@google.com <maf@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-07-23 23:33:21 +0000
committermaf@google.com <maf@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-07-23 23:33:21 +0000
commitf44ea0d6f8a6da9b98ecfe3fc30235ef65e28635 (patch)
tree438d764fb3ab89a93ee91d3764c053abf701ade0 /chrome/browser/views
parent26cd5c815ddc94fe643cb7acf23731d2a2d80915 (diff)
downloadchromium_src-f44ea0d6f8a6da9b98ecfe3fc30235ef65e28635.zip
chromium_src-f44ea0d6f8a6da9b98ecfe3fc30235ef65e28635.tar.gz
chromium_src-f44ea0d6f8a6da9b98ecfe3fc30235ef65e28635.tar.bz2
Add a boolean parameter to Client::RenderClient() to choose whether to
make the javascript render callback or not. Generally you want to pass true, but if the render is happening in non-windowed mode (eg on a Mac) and is in response to an update event rather than a timer, it can be useful to pass false to prevent the javascript code triggering another update and causing an infinite calback loop. Case in point is the custom camera example, which modifies some HTML form text fields on render callback, which on Firefox causes a plugin invalidation and round and round we would go. Review URL: http://codereview.chromium.org/159181 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@21473 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/views')
0 files changed, 0 insertions, 0 deletions