| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
BUG=180555
Review URL: https://chromiumcodereview.appspot.com/12531004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186793 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=180058
Review URL: https://chromiumcodereview.appspot.com/12512003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186792 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having an instance ID is equivalent of navigate_src_sent_. Thus,
we can simply check if we have a non-zero instance ID.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/12452005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186791 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The identity API is moving to prompting for scopes at runtime only. This
change removes OAuth prompts from all app install flows. The Identity API
still displays the extension install dialog at runtime for its prompts.
OAuth code will be removed from the extension install dialog in the next
change, which will switch Identity to web-based dialogs.
BUG=124493
Review URL: https://chromiumcodereview.appspot.com/12433009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186790 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
PerformSelectorIgnoringExceptions() -> RunBlockIgnoringExceptions(),
as the block version is more generalized.
BUG=none
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12342021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186789 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the related switch to Android command line and also
implements InstantExtendedEnabledParam() for iOS and Android in a such a
way to add the necessary Replacement param if query extraction is enabled
and the base url is secure.
BUG=177333
TBR=bartfab@chromium.org
Review URL: https://chromiumcodereview.appspot.com/12319124
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186788 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Helps test that the shim and the compiler work together
correctly. At this moment, this does not use the in-browser
translator, since the ppapi browser test nexe is large and
the translation cache does not get shared between
invocations. See comments in bug 2484 about this.
BUG= https://code.google.com/p/nativeclient/issues/detail?id=2484
TEST= browser_tests --gtest_filter=*PNaCl*
Review URL: https://chromiumcodereview.appspot.com/12288013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186787 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The autofill controller should always handle all hides,
to ensure that everything is properly hidden.
TBR=isherman@chromium.org
BUG=178564, 178504
Review URL: https://chromiumcodereview.appspot.com/12556002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186784 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some types of async transfers need a separate binding step on the main
graphics context before the target texture becomes valid. Previously
this binding was performed inside MakeCurrent. This was sufficient
because clients were only informed of async transfer completions during
MakeCurrent.
However, the recently added WaitAsyncTexImage2DCHROMIUM made it possible
for clients to submit rendering commands that used the results of async
transfers without an intermediate call to MakeCurrent. The problem is
that in this case the binding step was not performed and we ended up
using a texture with incorrect contents.
This patch fixes the problem by performing async transfer binding after
we have waited for their completion.
BUG=161828
Review URL: https://chromiumcodereview.appspot.com/12476004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186783 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=180675
Review URL: https://chromiumcodereview.appspot.com/12549008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186781 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=none
Review URL: https://codereview.chromium.org/12463022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186780 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=178176
TEST=crash from that bug should disappear from newer builds on Windows
Review URL: https://codereview.chromium.org/12630006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186779 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New audio indicator icons:
- more frames, from 6 to 24
- switch to 16x16 to match fav icon sizes
The 2nd change also fixes a problem where we were drawing the 2x icon in 1x mode.
BUG=3541
Review URL: https://codereview.chromium.org/12545015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186778 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HostContentSettingsMap::RegisterExtensionService is the final piece of
initialization in this class, after which content_settings_providers_
is immutable, and so can be used from multiple threads without
locking. This assert verifies that the member is only accessed from a
single thread before initialization completes. The previous assert
(documented in the bug) checked that it was never read before
initialization, which was incorrect, it does get read but only by the
same thread that constructs and initializes it.
BUG=176315
Review URL: https://codereview.chromium.org/12553003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186777 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This memory leak was only happening when a fatal error was detected,
because the method was returning false in the middle of updating the
tree, sometimes leaving an allocated object without a parent.
Now the method only has two returns: once at the top, if a duplicate
child id is found, before any new memory has been allocated, and again
at the very bottom, if a reparented child id was found and skipped.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/12570004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186776 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This defines RenderWidgetCompositor::registerForAnimations,
which associates the LayerAnimationController of
newly-created cc::Layers with the AnimationRegistrar of the
RenderWidgetCompositor's LayerTreeHost. This also makes
cc::Layer::addAnimation accept animations whenever the
layer's LayerAnimationController has an AnimationRegistrar,
and makes LayerTreeHost only create an AnimationRegistrar
when accelerated animations are enabled.
Note that this is expected to regress Robohornet Pro by
about 16%: because of
https://bugs.webkit.org/show_bug.cgi?id=111617, Robohornet
Pro takes longer to complete when its animations are
accelerated. However, animations during this test (and on
other pages where animations are added to orphan layers)
will now be much smoother.
BUG=129683,179196
Review URL: https://chromiumcodereview.appspot.com/12388093
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186775 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
WebKit's V8/Binding code has changed so old stacks no longer
match. Update the suppressions accordingly.
BUG=162829
TBR=thestig@chromium.org
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12432010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186774 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Windows: Only collect D3D11 UMA stats if the GPU process launches and initializes successfully.
>
> DisplayLink seems to make D3D initialization crash. It turns out we have the same issue with D3D9 as well. However, in the case of D3D9, the GPU process tends to crash first, causing the browser process to not use D3D for anything. By waiting to see whether the GPU process crashes, the browser process should not crash (often) if a problematic version of DisplayLink is installed.
>
> BUG=175525
>
> Review URL: https://chromiumcodereview.appspot.com/12340089
BUG=180951
TBR=apatrick@chromium.org
Review URL: https://codereview.chromium.org/12635005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186773 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=180614
TEST=none, since not reproducible
Review URL: https://chromiumcodereview.appspot.com/12544008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186772 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also renames two Linux-sandboxing-related lists to use
underscores instead of hyphens to match the naming style
used elsewhere in the file.
BUG=none
TBR=agl@chromium.org
Review URL: https://chromiumcodereview.appspot.com/12614008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186771 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
follows immediately after 'mouseup'. swallowDoubleClick worked well in that case (it set initial click count to 0 while handling the 'mouseup' event and then increased it to 1 or above while handling the immediatelly following click). However the 'undo delete' menu item handler prevents firing the 'click' event (I found that commenting out 'updateCanExecute' restores it). It's why next click with click count = 1 was ignored.
This code works whether click event follows after mouseup event or not.
BUG=172580
TEST=Check the scenario described in the bug. Check doubleclick on a context menu (bug 140364).
Review URL: https://chromiumcodereview.appspot.com/12614002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186770 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Look like we're trying to run 32-bit plugins for these,
which we don't support on Win64 yet.
BUG=180861
R=piman@chromium.org
Review URL: https://chromiumcodereview.appspot.com/12610005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186769 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove a couple of unnecessary includes, write DEPS that allows
includes of files that will move to //components/autofill, and add a
temporary allowance for an include we'll get rid of by moving
Autofill-specific switches to a header in the Autofill component.
Also, mark include of GaiaUrls file as permanently allowed, as I don't
think there was any plan to get rid of this.
TBR=ben@chromium.org
BUG=140037
Review URL: https://chromiumcodereview.appspot.com/12550007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186768 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=dewittj@chromium.org
Review URL: https://codereview.chromium.org/12631005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186766 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186765 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=None
Review URL: https://chromiumcodereview.appspot.com/12476020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186764 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://trac.webkit.org/log/?rev=145051&stop_rev=145027&verbose=on
TBR=
BUG=
Review URL: https://codereview.chromium.org/12545016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186763 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
R=vandebo@chromium.org
BUG=173953
Review URL: https://chromiumcodereview.appspot.com/12450005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186762 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test didn't fail if it was run by itself. It turns out that if the previous
test didn't call driver.Quit(), an ExecuteScript() call in the following test
wouldn't be executed correctly.
TEST=chrome/test/chromedriver/run_py_tests.py --chromedriver=out/Release/libchromedriver2.so --chrome=out/Release/chrome
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12446006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186761 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
TBR=dewittj@chromium.org
BUG=178511
Review URL: https://codereview.chromium.org/12634005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186759 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Speculative revert. The tree went red at the time this change was checked in, and multiple GpuFeatureTests started failing consistently.
Example failure: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=@DEPS - chromium.org&testType=browser_tests&tests=GpuFeatureTest.WebGLAllowed
If you look at the first Win Aura Tests (2) fail, you get the following blamelist range: 186630 to 186619.
> Use gpu::Mailbox in IPCs instead of std::string
>
> gpu::Mailbox is safer since the size is checked in the deserializer. It's also
> overall less code.
>
> BUG=None
>
>
> Review URL: https://chromiumcodereview.appspot.com/12440005
TBR=piman@chromium.org
Review URL: https://codereview.chromium.org/12612005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186758 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Got broken by http://crrev.com/186737
BUG=none
TEST=run the test locally
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12635002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186749 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=180937
> Set up V8 bindings for extension/app APIs when they're first used, not on
> context creation. This should gives us a significant reduction in extension/app
> startup time and slightly better memory usage.
>
> It also gives us better error messages, the chance to complete the
> implementation of API features, and eventually the ability to expose select
> extension APIs (e.g. extension.sendMessage) to web pages.
>
> Resubmitting: changes made to resubmit this patch reviewed in: https://codereview.chromium.org/12378077/
>
> BUG=163678,120070,55316,177163
> TBR=ben@chromium.org
>
> Review URL: https://chromiumcodereview.appspot.com/11571014
TBR=cduvall@chromium.org
Review URL: https://codereview.chromium.org/12632004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186748 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
As chrome remote debugging port is hardcoded as 33081, we have to quit chrome after every test, even when the test fails.
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12593002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186747 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
checklicenses.py passes for ppapi directories now, so we don't need these
suppressions any longer.
BUG=98107
Review URL: https://chromiumcodereview.appspot.com/12389087
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186745 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
TBR=sky@chromium.org, yoz@chromium.org
BUG=178511
Review URL: https://codereview.chromium.org/12313115
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186744 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=none
Review URL: https://codereview.chromium.org/12476005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186743 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes many tests that were relying directly on
BalloonCollectionNotificationManager, since that is now defunct on
platforms with ENABLE_MESSAGE_CENTER.
It also disables some tests that no longer make sense.
BUG=169538
Review URL: https://chromiumcodereview.appspot.com/12472007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186742 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186741 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TBR=garykac@chromium.org
Review URL: https://codereview.chromium.org/12616005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186740 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
R=jkummerow@chromium.org
Review URL: https://chromiumcodereview.appspot.com/12613009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186739 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://chromiumcodereview.appspot.com/12390077
THe code in question doesn't account for the utility process.
BUG=180926
TBR=sievers
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/12627002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186738 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=180293
TEST=Press Alt+Shift+M after login, and confirm that Files.app launches.
Review URL: https://chromiumcodereview.appspot.com/12589004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186737 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Occassionally we switch to another channel after processing a
SwapBuffers but before processing the Echo. This fast tracks the EchoACK
and makes it more reliable for detecting if a SwapBuffers is blocked on
a vblank.
Review URL: https://chromiumcodereview.appspot.com/12544003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186736 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a pretty simple translation of the library stripping into
python. With the component build, this step will become a bit more
complex, and so I'd much rather it be in python than shell script.
BUG=158821
Review URL: https://chromiumcodereview.appspot.com/12330112
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186735 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=174228
R=jamescook@chromium.org,jennyz@chromium.org
Review URL: https://chromiumcodereview.appspot.com/12549012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186734 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that Google Chrome 26 is stable, the intros need to reflect this clearly.
I also added a release note to extension's 'What's New' for pushMessaging API,
which went stable in M24.
Note that I did not add lots more information about apps-specific APIs to extension's 'What's New', as so far, this doc has been for extension APIs.
Working on a new way to document and promote changes across apps and extensions, so holding off on putting a lot of effort into the existing doc.
Review URL: https://codereview.chromium.org/12433018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186733 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added a new fixture that has entries spread over different weeks and months
to enable testing the grouped and ranged features of the history page.
Also added some tests that check those features using the new fixture.
R=dubroy@chromium.org
BUG=170690
out/Debug/browser_tests --gtest_filter=RangeHistoryWebUITest.*
Review URL: https://chromiumcodereview.appspot.com/12261013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186732 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chrome on Linux. We need the development header to build chromium.
This is needed for https://codereview.chromium.org/12310101/
TBR=dalecurtis@chromium.org
BUG=178101
Review URL: https://chromiumcodereview.appspot.com/12613005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186731 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/12463004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186728 0039d316-1c4b-4281-b951-d872f2087c98
|