GitLab

Also, when we cleanup tilings on the active twin, we use the pending
twin's ideal contents scale. But when the twin !CanHavTilings() there
is no need to use that ideal scale and save tilings.

R=enne@chromium.org, enne

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

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

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

BUG=385222
TBR=glider@chromium.org
NOTRY=true

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

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

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

Simplified the updateGetUserMediaConstraints function.

BUG=None
Test=gjslint, manually setup a call, verified that the constraints are
updated correctly.

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

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

BUG=386522
TEST=run the test

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

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

Mouse events generated from Ozone do not have a NativeEvent associated
with them and so they need to go through the non native event based flow
in the multi-monitor warping code. With this change it is now possible
to move the pointer from one display to the next under Ozone.

TEST=On link_freon attach a second display and move the pointer from
one display to the other.
BUG=361144

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

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

Previously Gallery.app tried to create a new element when an image is updated,
but the new element does not added to DOM.

This CL change the behavior so that the app reuses an existing element.

BUG=385535
TEST=manually

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

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

This doesn't hook up visitedlink_renderer since it depends on blink.

BUG=
R=jamesr@chromium.org

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

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

BUG=

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

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

Some of the mojo templates want to put generated files in the directory
corresponding to the source file, rather than the directory containing the
BUILD file. Previously, this required putting the BUILD files in the same
directory.

This patch adds the ability to specify the generated file directory
corresponding to the input file in the action_foreach file templates so this
can be expressed naturally.

For parity, it also adds qquerying for this information via get_path_info.

BUG=
R=cjhopman@chromium.org

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

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

Also:
* Move SetMinimumLogLevel() into MojoLogger itself. (This is somewhat
  unfortunate, since may not be thread-safe -- in particular, when
  sharing a copy of base's logging as in a component=shared_library
  build, it becomes blatantly unsafe. Thus it's of slightly dubious
  value. But it's where it belongs logically. Of course, sharing a log
  level across applications that are cohabiting a process is dubious.
  Avoiding this would mean at least layering a log level on top of
  Chromium's.)
* Allow the (standalone) Environment's choices for default AsyncWaiter
  and/or Logger to be overridden.

R=darin@chromium.org

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

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

This adds a few helper functions to WidgetTest for getting information
from a native widget and makes widget_test.h responsible for defining
typedefs for PlatformNativeWidget and (when not ChromeOS)
PlatformDesktopNativeWidget.

4 aura-specific tests (that are #ifdefd out on ChromeOS) that use
DesktopAuraTopLevelWindowTest are moved from widget/widget_unittest.cc
to widget/desktop_aura/desktop_native_widget_aura_unittest.cc

widget_unittests.cc doesn't yet compile on Mac with this alone due to
the event generator (addressed in CL/322893005).

BUG=378134
TEST=views_unittests

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

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

If current wallpaper is set by third party app/extension, show its name
in wallpaper picker.


BUG=360695

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

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

R=ajwong
TBR=ajwong

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

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

This also increments the app list shortcut version.

This will trigger a rebuild of all app shims.

This also disables updating all shortcuts in tests.

BUG=353047

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

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

Also switch bionic_canary over to being updated automatically.

pepper_canary used to update based on the Chrome canary version, but that often
prevents pepper_canary from updating as quickly. It also is unlikely that a
newer pepper_canary than Chrome canary will cause any issues.

This change makes pepper_canary (and bionic_canary) update based solely on which
bundles are available in the cloud storage bucket.

BUG=none
R=sbc@chromium.org
TEST=update_nacl_manifest_test.py

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

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

Update the list of file permissions in the App Info dialog to elide in
the middle, to better match the UI mocks of the dialog.

Screenshots on bug.

BUG=385978

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

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

No intended behavior change.

BUG=none

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

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

BUG=

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

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

Previously, OpaqueBrowserFrameView was being used for popups and hosted apps. So popups and hosted apps would only use the native frame when the "Use system titlebars and borders" option was selected.

BUG=376137
TEST=Manual, see bug (Must use i3 window manager)

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

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

Same owners as the one in enhanced_bookmarks/OWNERS.

BUG=None
R=blundell@chromium.org

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

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

Show error when an http:// URL is passed as parameter
to chrome.app.window.create().

BUG=241487

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

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

TBR=dnicoara
NOTRY=true
BUG=

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

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

Listen to the full screen event, then if so, close the bubble.

BUG=326081

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

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

This is not necessary, and causes the entire ash mode to get WS_CAPTION
as ash mode shares a single HWND.

BUG=385557

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

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

to ensure that we don't typically send out incomplete packets.

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

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

This CL aims to fix the bug that when webview guest create a SharedWorker, the sctipt file of SharedWorker can not be loaded. 

The SharedWorker lives in a separate render process as the webview who creates it. Because  url_request_util::AllowCrossRendererResourceLoad（...） doesn't consider that the render process of the SharedWorker  is a guest, so it denies the load of SharedWorker's script.

So we introduce webview partition id map in ExtensitonRenderState. When loading a SharedWorker script, we will check whether the script file is in the accessible resource of given "Partition ID", and decide whether it can be loaded or not. 

BUG=

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

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

When settings in a window is enabled, add a back button to the devices
page. This helps because the window has no address bar. See bug for
screenshot.

Longer-term, the devices page should show as an overlay in Settings
rather than load as a new page.

RTL is not enabled for this page; see issue 386020.

BUG=384333
R=noamsml@chromium.org,oshima@chromium.org

+oshima@ for icon. Oshima, is theme_resources the right place for this?
+stevenjb@ for browser shenanigans in local_discovery_ui.cc.

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

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

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

This resulted in incorrect processing and things like entering not
working.

BUG=386256
TEST=none
R=ben@chromium.org, darin@chromium.org

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

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

TBR=bruening@chromium.org
BUG=NONE

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

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

BUG=364365

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

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

Mostly renumbered and restructured grammar productions.  Notable changes:

- add support for static attributes via StaticMember
- add support for built-in types ByteString and RegExp
- allow trailing comma in enum declarations

Depends on:
IDL parser: drop AttributeOrOperation and StaticAttribute overrides
https://codereview.chromium.org/336733002/
...or else breaks Blink compile.

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

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

 * If NSS version doesn't support AES-GCM
 * If NSS version doesn't support RSA-OAEP

BUG=384485

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

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

Skia's save() SaveFlags bits are deprecated. At this
point all callers have been updated to always pass kMatrixClip, but
SkCanvas subclasses also need to use the new willSave() API.

(depends on https://codereview.chromium.org/338833003/ rolling)

BUG=skia:2297
R=piman@chromium.org, reed@google.com, robertphillips@google.com

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

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

SyncTaskRunner's task invocation tend to grow call stack deeper.
This CL clears the call stack per task to avoid stack overflow.

BUG=344769

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

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

Should not affect behaviour of the normal app list. The experimental app
list now transitions pages in from the correct side of the screen,
instead of simply sliding pages out to the left.

BUG=377381

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

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

BUG=347425
TEST=./unit_tests --gtest_filter="MetadataDatabaseTest.*:MetadataDatabaseIndexTest.*"

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

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

Honour the safe browsing opt out and report on incidents that arrive
before profile initialization is complete.

BUG=383039,383365
R=mattm@chromium.org, noms@chromium.org
TBR=asvitkine@chromium.org

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

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

mojo_common can not depends on embedder, as standalone application must
depends on it. channel_init is in fact a part of the embedder.

R=viettrungluu@chromium.org
TBR=darin@chromium.org

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

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

Currently, we use wrong storage type for nested arrays. For example, the storage
type of the outer array of int8[][] is
StructPointer<Array_Data<int8_t>>. After this CL it will be
ArrayPointer<int8_t>.

The current code works because StructPointer happens to be of the same
size as ArrayPointer.

(The newly-added tests pass with/without this CL. But I think it is good
to have them.)

BUG=None
TEST=None

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

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