GitLab

This includes the following changes:
a1851e8  Fixes for re-enabling more MSVC level 4 warnings: angle/ edition
6518fe2  Moved TextureStorage and Image into d3d
d4cfa57  Move more draw call validation to the API.
f6d38b0  Fix CollectVariablesTest GCC/Clang compile errors.
4e1fd41  Store a map of interface block registers.
829e89e  Add a default constructor to sh::ShaderVariable.
d5512cd  Collect shader outputs and interface block information.
0b7e5d8  Fix 64-bit warnings.
c0b9ef4  Split Caps into Caps, Extensions and TextureFormatCaps.
57f9b6d  Clean up generatemip.h.
86846e2  Clean up the functions in loadimage.h/cpp.
2a6564e  Fix build errors in validationES.cpp.
e92a354  Remove redundant FBO query methods.
55ec3b1  Refactor common attachment validation to base method.
23a8a43b  Store compact and expanded shader variables.
aae65a4  Add caps for texture size limits and other caps in the 6.28 table.
77f7485  Add a GetVariableInfo helper method.
93455eb  Add missing limits include to angleutils.h
4667c45  Refactor style in VariableInfo.cpp.
53cb14d  Share ArrayString and Str helper methods.
b23375f  Fixed an issue with Streaming Vertex data overflowing it's buffer.
aa7e166  Improve the const correctness.
b447227  Add a ValidateAttachmentTarget helper method.
570f7c8  Add helper methods for FBO attachment validation.
a328d56  Removed sampler state getters and setters from gl::Texture

BUG=none
TEST=none

Review URL: https://codereview.chromium.org/399733006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283877 0039d316-1c4b-4281-b951-d872f2087c98

A test window is just a path to write an image file to. Each window has
a unique image path.

BUG=392280
TEST=built with chromeos==1 use_ozone==1 & ran test platform
NOTRY=true

depends on https://codereview.chromium.org/375053002/

Review URL: https://codereview.chromium.org/377973005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283875 0039d316-1c4b-4281-b951-d872f2087c98

Initialize the input-method using ui::InitializeInputMethodForTesting()
before creating the input method.

BUG=none
R=sky@chromium.org

Review URL: https://codereview.chromium.org/400713002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283874 0039d316-1c4b-4281-b951-d872f2087c98

In overscroll mode, any window with web contents that overlaps the virtual keyboard has insets in order to facilitate scrolling to the bottom of the document.  These insets are updated whenever the keyboard is shown or hidden.  This patch adds another update in the event that a window moves while the keyboard is visible.  This case can occur after a screen rotation while the keyboard is shown.


BUG=391337

Review URL: https://codereview.chromium.org/368323002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283873 0039d316-1c4b-4281-b951-d872f2087c98

There is an unused implementation of this method,
which can be removed.

BUG=none
TEST=none

Review URL: https://codereview.chromium.org/397283004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283871 0039d316-1c4b-4281-b951-d872f2087c98

Now only --disable-threaded-compositing exists, which is only present
for layout tests. The --enable-threaded-compositing flag moves to
become a content shell flag only, as it's only used for DumpRenderTree.

Change any checks in the renderer process for kEnableThreadedCompositing
to instead be !kDisableThreadedCompositing since that is the only
flag left.

Remove the whole threaded compositing thing from about:gpu and
about:flags.

R=piman
BUG=384381,346363

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=278151

Review URL: https://codereview.chromium.org/337783002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283870 0039d316-1c4b-4281-b951-d872f2087c98

File paths take too long to look up. Instead, use the file id versions.

BUG=385307

Review URL: https://codereview.chromium.org/378263002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283869 0039d316-1c4b-4281-b951-d872f2087c98

UserNetworkConfigurationUpdater::SetSkipCertificateImporterCreationForTest
is not needed anymore, so it's safe to remove it and cleanup tests
using it.

BUG=None

Review URL: https://codereview.chromium.org/325313004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283868 0039d316-1c4b-4281-b951-d872f2087c98

BUG=372843

Review URL: https://codereview.chromium.org/383023002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283866 0039d316-1c4b-4281-b951-d872f2087c98

We will need this for networkingPrivate so that we can notify observers
when Device properties of a Cellular network change.

BUG=none

Review URL: https://codereview.chromium.org/395523004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283863 0039d316-1c4b-4281-b951-d872f2087c98

Setting a layer-hosting NSView's CALayer's geometry flipping has a lot
of unexpected side-effects, and is proving unsafe, especially if that
NSView will have sub-views.

Add a level of indirection where the hosted layer is not flipped, but it
has a sub-layer that is flipped, off of which the layers for composited
content are attached.

BUG=392952

Review URL: https://codereview.chromium.org/392143002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283862 0039d316-1c4b-4281-b951-d872f2087c98

We'll want to break up ppb_nacl_private_impl.cc instead of lumping things into
one large file. This change makes the method for getting CPU feature attributes
easier to reuse, and renames the sandbox_arch.{cc,h} files in the process.

This is split off from a larger change to remove FileDownloader in the trusted
plugin.

BUG=370556
R=bbudge@chromium.org

Review URL: https://codereview.chromium.org/399983002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283861 0039d316-1c4b-4281-b951-d872f2087c98

BUG=386785

Review URL: https://codereview.chromium.org/394353003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283860 0039d316-1c4b-4281-b951-d872f2087c98

This reverts commit 93a9886b.

This CL makes mean_input_event_latency crazy.

BUG=394889
TBR=skyostil
NOTRY=true

Review URL: https://codereview.chromium.org/400533006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283859 0039d316-1c4b-4281-b951-d872f2087c98

BUG=392280
TEST=built with chromeos==1 use_ozone==1 & ran caca on X11
NOTRY=true

Review URL: https://codereview.chromium.org/387953004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283858 0039d316-1c4b-4281-b951-d872f2087c98

This one change should have been part of an earlier CL (r274947).

BUG=326304

Review URL: https://codereview.chromium.org/393083003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283857 0039d316-1c4b-4281-b951-d872f2087c98

Trigger to download the high resolution avatar immediately, after a new profile has been created.

BUG=391696
TEST=manually tested, see repro steps in the bug.

Review URL: https://codereview.chromium.org/380643002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283856 0039d316-1c4b-4281-b951-d872f2087c98

I came across this while trying to figure out how to make entry points work for
the trusted plugin. It's confusing to have these gypi variables around
when they're not used anywhere.

BUG=
R=bbudge@chromium.org

Review URL: https://codereview.chromium.org/405433006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283855 0039d316-1c4b-4281-b951-d872f2087c98

In order to allow MediaKeySession to be created only when resolving
the promise, add the ability to set the client callback interface on
WebContentDecryptionModuleSessionImpl after the object is created.

This will be used in a subsequent CL to update blink. Requires a third
change to remove the old methods once blink is updated.

BUG=358271
TEST=EME layouts tests pass

Review URL: https://codereview.chromium.org/380953002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283854 0039d316-1c4b-4281-b951-d872f2087c98

TestContextProvider returns NULL GrContext now, adding todo's to make
it clear that code path is used only because of that shortcoming.
BUG=

Review URL: https://codereview.chromium.org/396853003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283853 0039d316-1c4b-4281-b951-d872f2087c98

files when refreshing extensions page.

Screenshot:
http://i.imgur.com/02tzoUK.png

BUG=375276

Review URL: https://codereview.chromium.org/342003005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283852 0039d316-1c4b-4281-b951-d872f2087c98

BUG=None
TBR=sadrul@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=283774

Review URL: https://codereview.chromium.org/401613004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283851 0039d316-1c4b-4281-b951-d872f2087c98

This test measures how expensive it is to simply create a tiling raster
tile iterator.

Initial run from a macbook pro:
[ RUN      ] PictureLayerTilingPerfTest.TilingRasterTileIteratorConstruction
*RESULT tiling_raster_tile_iterator_construction: 0_0_100x100= 5843577 runs/s
*RESULT tiling_raster_tile_iterator_construction: 50_0_100x100= 5940125 runs/s
*RESULT tiling_raster_tile_iterator_construction: 100_0_100x100= 3772066.25 runs/s
*RESULT tiling_raster_tile_iterator_construction: 150_0_100x100= 3712790 runs/s
[       OK ] PictureLayerTilingPerfTest.TilingRasterTileIteratorConstruction (12713 ms)

We can see here that there is some cost (albeit small) associated
with the construction. If the viewport is off the layer bounds,
then we pay more to figure out where the first tile is.

This cost is paid for each tiling iterator that is created (typically two
per layer: high res and low res).

NOTE TO PERF SHERIFFS
--------------------
This patch removes tiling_raster_tile_iterator test and replaces it
it tiling_raster_tile_iterator_construct_and_iterate as well as
tiling_raster_tile_iterator_construct test.

R=reveman

Review URL: https://codereview.chromium.org/398073002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283850 0039d316-1c4b-4281-b951-d872f2087c98

BUG=None
R=danakj@chromium.org

Review URL: https://codereview.chromium.org/391343009

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283849 0039d316-1c4b-4281-b951-d872f2087c98

BUG=377813

Review URL: https://codereview.chromium.org/398073003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283848 0039d316-1c4b-4281-b951-d872f2087c98

BUG=386273

Review URL: https://codereview.chromium.org/344613003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283847 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283846 0039d316-1c4b-4281-b951-d872f2087c98

Failed WebRtcBrowserTest on android_dbg_triggered_tests.

> Switch to BoringSSL.
> 
> (This is a reland of r283542 which was reverted in r283591 because it
> broke the WebView build. The android_aosp trybots are broken[1] so this
> based on hope.)
> 
> This is a much larger change than its diff suggests. If it breaks
> something, please revert first and ask questions later.
> 
> [1] http://code.google.com/p/chromium/issues/detail?id=394597
> 
> BUG=none
> 
> Review URL: https://codereview.chromium.org/399993002

TBR=agl@chromium.org

Review URL: https://codereview.chromium.org/405503002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283845 0039d316-1c4b-4281-b951-d872f2087c98

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283844 0039d316-1c4b-4281-b951-d872f2087c98

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=178352:178380&mode=html
TBR=abarth@chromium.org,johnme@chromium.org,eseidel@chromium.org
BUG=

Review URL: https://codereview.chromium.org/400703004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283843 0039d316-1c4b-4281-b951-d872f2087c98

This modifies the eviction order to consider occlusion so that the
LayerEvictionTileIterator and TileManager::EvictionTileIterator will
evict occluded tiles before unoccluded tiles in the same priority bin.

The current eviction order is to evict tiles that are:
1. In a lower priority bin
2. Not required for activation
3. At worse resolution
4. Farther away from visible

This patch adds occlusion to the order to evict tiles that are:
1. In a lower priority bin
2. Not required for activation
3. At worse resolution
4. Occluded
5. Farther away from visible

This patch depends on https://codereview.chromium.org/374653003/ which
tracks occlusion per tree and stores the info on the Tile.

BUG=178971

Review URL: https://codereview.chromium.org/377793003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283842 0039d316-1c4b-4281-b951-d872f2087c98

BUG=392678

Review URL: https://codereview.chromium.org/386043006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283841 0039d316-1c4b-4281-b951-d872f2087c98

Moves all code remaining in sync/notifier to components/invalidation.
Updates gyp files, DEPS, and #includes accordingly.

In terms of program behavior, this should be one big no-op.  This CL
contains no non-trivial code changes.

In terms of the build system, this is a significant change.  Symbols
that were previously exported through sync_notifier and related targets
have moved into the components/invalidation related targets.  Some
SYNC_EXPORT macros have been replaced with INVALIDATION_EXPORT, which is
significant since INVALIDATION_EXPORT is currently a no-op but
SYNC_EXPORT has meaning under some build configurations.

Unlike most other files in sync/notifier, invalidation_util.{cc,h} was
moved to sync/internal_api/public/base.  This is so it could be
referenced from sync/internal_api/public/base/invalidation.cc.  This is
a slight regression, but it should be fixed in the next CL when we move
all invalidations-related code out of sync/internal_api.

TBR=rogerta,benwells
BUG=259559

Review URL: https://codereview.chromium.org/387733004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283840 0039d316-1c4b-4281-b951-d872f2087c98

This is necessary to handle context menu , popup menu etc.

BUG=380438

Review URL: https://codereview.chromium.org/396813003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283839 0039d316-1c4b-4281-b951-d872f2087c98

BUG=354841
NOTRY=True

Review URL: https://codereview.chromium.org/395133006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283838 0039d316-1c4b-4281-b951-d872f2087c98

There are situations where the pdf plugin will initialize itself in such a way
that it never notifies content/renderer/ that it has started. In so doing, it
also fails to send a stop message, since it tries to ensure it doesn't send
mismatched start/stop messages.

Print preview decides when to display the preview based on when loading
stops. Since this only considers the page's content and not the pdf plugin's
initialization, there is a race condition where we may try to preview before
the plugin is ready. In this cases, we show "Loading preivew..." and never load
the actual preview.

There is a hack in place in print_preview_web_helper.cc to delay the process of
showing the preview to maximize the chance that the pdf plugin will be ready.
This change should allow us to rip that out.

BUG=376969

Review URL: https://codereview.chromium.org/397713005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283837 0039d316-1c4b-4281-b951-d872f2087c98

If I type an exact query that I issued before, SearchProvider shouldn't
offer an extension to the autocompletion, even if that I issued that longer
query more recently.  This is counter to user's expectations: if I issued
the query before and type it again and hit enter, I should get that query.

I do not plan to bother running an experiment for this change.

BUG=246411

Review URL: https://codereview.chromium.org/397723003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283836 0039d316-1c4b-4281-b951-d872f2087c98

BUG=

Review URL: https://codereview.chromium.org/353063005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283835 0039d316-1c4b-4281-b951-d872f2087c98

BUG=394627
R=zea@chromium.org

Review URL: https://codereview.chromium.org/395413002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283833 0039d316-1c4b-4281-b951-d872f2087c98

Demonstrate in the NaCl SDK API demo for pp::Graphics2D how
to use full device resolution on HiDPI displays. For Graphics2D,
the example now calls pp::View::GetDeviceScale(), and creates
a Graphics 2D context with the correct number of pixels, as well
as show when to call pp::Graphics2D::SetScale().

It also scales the mouse position to the correct location and
increases the radius of the circle created in DrawMouse() to match.

BUG=144071,392557
TEST=Build NaCl SDK, run with --force-device-scale-factor=2

Review URL: https://codereview.chromium.org/397173003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283832 0039d316-1c4b-4281-b951-d872f2087c98