| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
offer to suppress dialogs if they're initiated by a user gesture.
BUG=263192
TEST=as in bug
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=220050
Review URL: https://chromiumcodereview.appspot.com/22909052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220258 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Plumb user_gesture up from Blink to the JavaScript dialog code, and don't offer to suppress dialogs if they're initiated by a user gesture.
>
> BUG=263192
> TEST=as in bug
>
> Review URL: https://chromiumcodereview.appspot.com/22909052
TBR=avi@chromium.org
Review URL: https://codereview.chromium.org/23483008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220062 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
offer to suppress dialogs if they're initiated by a user gesture.
BUG=263192
TEST=as in bug
Review URL: https://chromiumcodereview.appspot.com/22909052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220050 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=279929
Review URL: https://chromiumcodereview.appspot.com/22986033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219854 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reverted due to crashes under memory tools.
BUG=280138
> Remove the Extensions URLRequestContext.
>
> Though chrome-extension: scheme URLs support cookies, they do not share
> a namespace with http: and https:. In particular, chrome-extension://a and
> http://a should not have the same set of cookies.
>
> To enforce this, previously the code created a completely separate
> URLRequestContext for servicing chrome-extension: schemes. However,
> the code really only used this object as a method for conveying the
> correct cookie jar from Profile creation to a few spots where cookies
> were accessed; the rest of the URLRequestContext functionality was unused.
>
> This CL removes the Extensions URLRequestContext code and replaces it
> with APIs that directly expose the needed net::CookieStore.
>
> Lastly, CookieMonster::EnableFileScheme() is removed and
> CookieMonster::Delegate is renamed CookieMonsterDelegate.
>
> EnableFileScheme is an inherently racy API because
> CookieMonsters are creatable on all threads and this
> function sets an unprotected global flag. CookieMonsterDelegate
> is preferable to the nested interface because it can now be
> forward declared.
>
> TBRing darin and sky to cover the rest of the mechanical unittest changes.
>
> TBR=darin,sky
> BUG=158386,159193,57884
>
> Review URL: https://chromiumcodereview.appspot.com/12546016
TBR=ajwong@chromium.org
Review URL: https://codereview.chromium.org/23551005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219787 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Though chrome-extension: scheme URLs support cookies, they do not share
a namespace with http: and https:. In particular, chrome-extension://a and
http://a should not have the same set of cookies.
To enforce this, previously the code created a completely separate
URLRequestContext for servicing chrome-extension: schemes. However,
the code really only used this object as a method for conveying the
correct cookie jar from Profile creation to a few spots where cookies
were accessed; the rest of the URLRequestContext functionality was unused.
This CL removes the Extensions URLRequestContext code and replaces it
with APIs that directly expose the needed net::CookieStore.
Lastly, CookieMonster::EnableFileScheme() is removed and
CookieMonster::Delegate is renamed CookieMonsterDelegate.
EnableFileScheme is an inherently racy API because
CookieMonsters are creatable on all threads and this
function sets an unprotected global flag. CookieMonsterDelegate
is preferable to the nested interface because it can now be
forward declared.
TBRing darin and sky to cover the rest of the mechanical unittest changes.
TBR=darin,sky
BUG=158386,159193,57884
Review URL: https://chromiumcodereview.appspot.com/12546016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219709 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ObserverList::size.
See issue for rationale behind this change.
BUG=278526
TEST=no change
TBR=benm@chromium.org
(TBR'ing for prefs API change).
Review URL: https://chromiumcodereview.appspot.com/22986034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219622 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this CL, AwBrowserContext::CreateRequestContext will actually be responsible for creating the URLRequestContextGetter which makes it behave much closer to the coding pattern used by Profile.
This is necessary to unblock movement of the URLRequestContext creation into content.
BUG=159193
R=joth@chromium.org, mkosiba@chromium.org
Review URL: https://codereview.chromium.org/22812016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219620 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
SkBitmapDevice. Right now Skia has typedefs redirecting SkBaseDevice and SkBitmapDevice to SkDevice. This CL begins the Chromium-side renaming process in preparation for the real change (https://codereview.chromium.org/22978012/)
BUG=278148
Review URL: https://chromiumcodereview.appspot.com/22796028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219568 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=None
TBR=jam@chromium.org
Review URL: https://chromiumcodereview.appspot.com/23112033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219495 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=277245
We unintentionally defer/block requests that are internally generated
since these do not have a renderview process/view associated with
them. Fix this.
Review URL: https://chromiumcodereview.appspot.com/22866019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AwResourceDispatcherHostDelegate::DownloadStarting
The request may not have started, in which case we cannot ask for the
MIME type or response headers.
BUG=277744
Review URL: https://chromiumcodereview.appspot.com/23075018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219312 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we are not guaranteed to call RequestProcessGL on the UI
thread which is a threading bug that can cause coruption/crashes.
BUG=277055
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/23060021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218828 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apps call onPause/onResume to explicitly request
pausing/resuming per webview processing. But apps are not
required to call them.
Also window (not view) becomes invisible when the for
example, an app is put into the background.
Should use these signals to disable fallback tick, which is
normally used to ensure offscreen webviews still make
progress.
BUG=276104
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/23004005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218466 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make net::URLRequestFileJob pass a TaskRunner to FileStream, instead of using a deprecated FileStream constructor that depends on WorkerPool. This TaskRunner is obtained from the blocking pool where possible. Also, remove two explicit uses of WorkerPool in net/url_request/ and chrome/browser/.
Removes dependency on deprecated code. Also fixes memory leaks in unit tests caused by FileStream destruction tasks not running to completion in WorkerPool.
BUG=248513, 251774
Review URL: https://chromiumcodereview.appspot.com/22795006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218273 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Original commit at r216632.
This is causing more problem than it is fixing because of the random
clip and transform of the fallback tick is messing with the tiling
and scheduling policy. These are more serious than the original
problem it was trying to solve, to make progress faster for an
offscreen webview.
BUG=275226
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/23086003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218215 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=b/10312777
Review URL: https://chromiumcodereview.appspot.com/23012004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217862 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Follow up to https://codereview.chromium.org/20234002/ - the old
representation is no longer set so remove use of it.
TBR=boliu@chromium.org
BUG=
Review URL: https://chromiumcodereview.appspot.com/22778004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216949 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously the config and clip_region field formats depended on skia
internal implementation details. This patch decouples the interface
from the specific skia version in use.
BUG=
Review URL: https://chromiumcodereview.appspot.com/20234002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216841 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the capturePicture path to work fully even when using
mismatched skia version to the system. AwCreatePictureFunction is now
obsolete and can be removed in a followup.
BUG=b/9814370
Review URL: https://chromiumcodereview.appspot.com/22035002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216667 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When compositor needs BeginFrame, the blink main thread may
be blocked on a commit. Currently, we still delay a draw
until the next Draw or at least 20ms if draw never comes.
This CL changes the first fallback tick for when compositor
turns on NeedsBeginFrame to have 0 delay.
This also allows times for raster tasks to begin before the
real draw comes, significantly reducing flickering in some
situations. This also slightly more decouples BeginFrame
that the compositor needs to proceed, from Draws that are
initiated by embedding app.
Long term plan is to separate BeginFrame and BeginFrame
deadline, and we can trigger BeginFrame immediately, but
wait for Draw to trigger the deadline.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/22711002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216632 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only draw to the intersection of the clip and the visible
rect. This is an optimization that is not always correct,
but this matches better with existing behavior.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/22616006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216389 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Android can put the webview into an FBO, and compositor should draw into
the FBO instead of directly on screen. Use AwGLSurface and explicitly
set the FBO at the beginning of each hardware draw.
Add new APIs in GLInProcessContext and WGC3DIPCBI to allow the
underlying GLSurface to be created separately.
BUG=251501
Review URL: https://chromiumcodereview.appspot.com/22277004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216136 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL queries the content settings to see if getSources() is authorized
to fill in SourceInfo.label, and if not, clears the values before they are
sent to the renderer process.
BUG=240710
Review URL: https://chromiumcodereview.appspot.com/20848002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215991 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove obsolete kUseZeroCopyBuffers
Remove placeholder testing-webview-gl-mode, replace with dedicated
kDisableWebViewGLMode
Set the disable webGL flag in follow up to crrev.com/215135
BUG=b/10188126
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/22260002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215714 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a re-factoring of the GpuMemoryBuffer framework to support
different run-time buffer implementations.
This also adds a GpuMemoryBuffer type that is backed by standard
shared memory. This allows us exercise more code in unit tests.
TEST=gpu_unittests --gtest_filter=MockGpuMemoryBufferTest.Lifecycle
BUG=261649
Review URL: https://chromiumcodereview.appspot.com/20536006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215508 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Applications depending on webview to make progress while in
the background depends on this to be as fast as regular
draws. At 60fps, draws should be at least 16.6ms apart.
Reduce fallback tick to 20ms to be slightly more than the
period in draws.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/21884007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215495 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue here is that compositor assumes every draw to match the
viewport exactly, and thus the whole viewport is updated each
draw. But we could be asked to draw a subset of the visible
rect, so there is a mismatch between what is really drawn and
what compositor assume is drawn.
Simple damage tracking inside compositor will not work for
webview because of all the other ways the view could be drawn.
Here is a simple fix. Whenever webview is asked to draw a subset
of the visible rect, invalidate the whole visible rect, regardless
of whether the compositor needs draws.
The assumption here is that the problem only manifests if we draw
a subset of the visible rect, so simply ensure the whole visible
rect drawn is immediately after. Ideally it should only be done if
we can detect the case of mismatch between compositor and what is
drawn, but this requires damage tracking and work through all the
different ways we can draw.
New in reland:
Always query the global visible rect each time it is needed since
the original listener does not always fire when it changes.
BUG=264275
NOTRY=true
Previously committed at r214727
Review URL: https://chromiumcodereview.appspot.com/21191002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215474 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use this list of RequestProcessGL to drive GL in case when GL
is not allowed.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/21159005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215447 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were only saving and restoring the binding of the active texture, but
chromium clobbers all of them.
BUG=internal b/10146253
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/21977002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215387 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The android_webview implementation needs to handle root layer fling
Java-side. This is required for proper integration with the android
view system which requires the fling scroll offset update to be
performed as a result of the computeScroll method.
BUG=None
TEST=AndroidWebViewTest
Review URL: https://chromiumcodereview.appspot.com/20990009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215339 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Always need to save active texture and restore it before glBindTexture
since glBindTexture should restore to the app's active texture, not
what happens to be left by chromium.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/21640002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215182 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This separates the command buffer client and service portions in
GLInProcessContext.
It removes the 'big lock', which was used to flush commands instantly
and on the calling thread (GL client thread). Instead it now creates a
dedicated GPU thread.
For Android WebView, it further allows the GPU message loop to be
explicitly processed (because a context is only available at given times
on a specific thread).
BUG=246450,239760,234964
Review URL: https://chromiumcodereview.appspot.com/19522006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215144 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Caused regression in internal b/10086957
> [Android WebView] Handle clip size smaller than visible rect
>
> The issue here is that compositor assumes every draw to match the
> viewport exactly, and thus the whole viewport is updated each
> draw. But we could be asked to draw a subset of the visible
> rect, so there is a mismatch between what is really drawn and
> what compositor assume is drawn.
>
> Simple damage tracking inside compositor will not work for
> webview because of all the other ways the view could be drawn.
>
> Here is a simple fix. Whenever webview is asked to draw a subset
> of the visible rect, invalidate the whole visible rect, regardless
> of whether the compositor needs draws.
>
> The assumption here is that the problem only manifests if we draw
> a subset of the visible rect, so simply ensure the whole visible
> rect drawn is immediately after. Ideally it should only be done if
> we can detect the case of mismatch between compositor and what is
> drawn, but this requires damage tracking and work through all the
> different ways we can draw.
>
> BUG=264275
> NOTRY=true
>
> Review URL: https://chromiumcodereview.appspot.com/21191002
TBR=boliu@chromium.org
Review URL: https://codereview.chromium.org/21357005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214770 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue here is that compositor assumes every draw to match the
viewport exactly, and thus the whole viewport is updated each
draw. But we could be asked to draw a subset of the visible
rect, so there is a mismatch between what is really drawn and
what compositor assume is drawn.
Simple damage tracking inside compositor will not work for
webview because of all the other ways the view could be drawn.
Here is a simple fix. Whenever webview is asked to draw a subset
of the visible rect, invalidate the whole visible rect, regardless
of whether the compositor needs draws.
The assumption here is that the problem only manifests if we draw
a subset of the visible rect, so simply ensure the whole visible
rect drawn is immediately after. Ideally it should only be done if
we can detect the case of mismatch between compositor and what is
drawn, but this requires damage tracking and work through all the
different ways we can draw.
BUG=264275
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/21191002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214727 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This prevents a single WebContents from annoying the user with JavaScript alert loops, no matter what the page does in-between (e.g. reload, switch sites).
BUG=265475
TEST=as in bug
TBR=mnaganov@chromium.org
Review URL: https://chromiumcodereview.appspot.com/21111002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214697 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For non-rectangular clips, the Android framework populates the stencil
buffer before asking WebView to draw. This adds support for CC to use
an externally provided stencil buffer instead of always disabling
stencil test. This change is the final piece needed to make rotation
transforms work correctly.
New tests ExternalStencilPixelTest.*
NOTRY=true
BUG=264053
R=danakj@chromium.org, joth@chromium.org, tedchoc@chromium.org
Review URL: https://codereview.chromium.org/20579004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214416 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Minor cleanups after r213771.
BUG=
R=joth@chromium.org
Review URL: https://codereview.chromium.org/21160002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214387 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Capturing the whole content, and starting the capture from the origin.
BUG=224003
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/19864002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214151 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Used for in-process GpuMemoryBuffer creation.
TEST=gpu_unittests --gtest_filter=MockGpuMemoryBufferTest.Lifecycle
BUG=261649
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/20658002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214136 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, we only block the creation of the WebContents but not the
creation of the RenderView. By moving the check to the IO thread, we
already block the creation of the RenderView.
BUG=38458
TBR=jam@chromium.org
TEST=BetterPopupBlockerTest.*
Review URL: https://codereview.chromium.org/20745002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214041 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this, we were only invalidating the clip rect in
DrawGL, which may not be the whole viewport. Now always
invalidate the global visible rect instead.
Also make physical backing size match view size, since
we are no longer using browser compositor.
BUG=264275
NOTRY=true
R=joth@chromium.org
Review URL: https://codereview.chromium.org/20388002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213771 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inside OnDraw, RequestDrawGL can fail and return false, which means
there will not be a follow up DrawGL call to actually trigger the draw,
but the FallbackTick is cancelled anyway. Fix by moving the cancel
inside DrawSWInteral to reflect we only want to cancel when we actually
draw.
BUG=internal b/9978808
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/19509007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213302 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Restores state that matches ContextState::RestoreGlobalState
with some exceptions.
Also remove some unneeded states from MODE_DRAW.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/19787007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213273 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
Final call into WebKit API ommitted as it depends on blink change https://codereview.chromium.org/19883002/
BUG=263263
Review URL: https://chromiumcodereview.appspot.com/19693016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213255 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The default implementation of DownloadManagerDelegate::GetNextId just
returns kInvalidId and so is causing this DCHECK. Fix by overriding in
AwDownloadManagerDelegate with a static variable implementation similar
to content shell.
See bug for details why it's not turning android bots red.
BUG=262184
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/19796004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212615 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Once we reveive a new favicon for a navigation, insert it into
the NavigationEntry.
BUG=b/9121594
Review URL: https://chromiumcodereview.appspot.com/19528004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212555 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
independent of whether the compositor is generating frames
BUG=232944
Review URL: https://chromiumcodereview.appspot.com/16958012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212526 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is useful for debugging by either adding to traces or
to error logs. It's not called anywhere it should be stripped
normally be stripped linker.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/19690002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212462 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DrawGL can be called without OnDraw, so if FallbackTickFired can be
called if DrawGL sets continuous_invalidate_ to false.
Add a DCHECK that FallbackTickFired does not run unnecessarily.
BUG=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/19567003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212290 0039d316-1c4b-4281-b951-d872f2087c98
|