GitLab

focus_manager.js with it.

R=arv@chromium.org
BUG=393873
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293590}

Remove the existing blacklist and whitelist allowed futex operations instead.
The semantics change a little bit as none of the "priority inheritance" operations
are allowed.

BUG=408847
R=mdempsky@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293589}

Recently string containing the SVN revision has changed. This change handles
both. Examples below.
Old: https://chromium.googlesource.com/chromium/src/+/01188669a2b154818e5db03cc36fb2dd23b8d947
New: https://chromium.googlesource.com/chromium/src/+/13cb79e07dcf1138a35a82e312aea265b06e8879

BUG=None
NOTRY=True

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

Cr-Commit-Position: refs/heads/master@{#293588}

Revert of Revert of Use SkSurface and SkImage instead of SkGpuDevice and SkBitmap in cc. (patchset #1 id:1 of https://codereview.chromium.org/546073002/)

Reason for revert:
This revert did not fix the pixel tests

Original issue's description:
> Revert of Use SkSurface and SkImage instead of SkGpuDevice and SkBitmap in cc. (patchset #5 id:80001 of https://codereview.chromium.org/520793002/)
>
> Reason for revert:
> Looks like it may have broken the layout tests.
>
> http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.7/builds/31264
>
> Original issue's description:
> > Use SkSurface and SkImage instead of SkGpuDevice and SkBitmap in cc.
> >
> > Committed: https://chromium.googlesource.com/chromium/src/+/37ffe8f81510bbfb82b48640aa96fe7e51efc654
>
> TBR=enne@chromium.org,senorblanco@chromium.org,sugoi@chromium.org,danakj@chromium.org
> NOTREECHECKS=true
> NOTRY=true
>
> Committed: https://chromium.googlesource.com/chromium/src/+/cea33af6d0b2c2c1805ef016da5161fc0ed540a0

TBR=enne@chromium.org,senorblanco@chromium.org,sugoi@chromium.org,danakj@chromium.org,robertphillips@google.com,reveman@chromium.org,bsalomon@google.com
NOTREECHECKS=true
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293587}

Switch to updated battery icons with less-opaque backgrounds
that are more visible against the white notification
background.

BUG=166645
R=stevenjb@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293586}

https://chromium.googlesource.com/chromium/blink/+log/dcd4f892fb78a6f808982633fbc7398714f157be..86ce4af33b763b24cf2365d8cd19a2ebade676c3
TBR=arv@chromium.org,keishi@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293585}

BUG=1
TBR=mal@chromium.org
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293584}

Adding support for the optional_field_style=reftypes flag.
This is needed for the invalidation client which expects
"boxed" types (e.g., Boolean rather than boolean) for
primitive fields, and depends on null comparisons to
determine whether or not a field is set.

BUG=377891,411282
R=nyquist@chromium.org

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

Patch from Colin Meek <meek@chromium.org>.

Cr-Commit-Position: refs/heads/master@{#293583}

The whitelist allows the alpha_enabled flag to be used on Beta and Stable
channels.

BUG=410550
TBR=jackhou@chromium.org, benwells@chromium.org
TEST=verify on Chrome OS device that wallpaper picker works on Beta channel.

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

Cr-Commit-Position: refs/heads/master@{#293582}

Build spew goes from 1.3K to 0.5K lines.

BUG=411461
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293581}

clang didn't like the reinterpret_cast either:
..\..\sandbox\win\sandbox_poc\pocdll\registry.cc(24,10) :  error(clang): case value is not a constant expression
    case reinterpret_cast<LONG_PTR>(HKEY_USERS):
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
..\..\sandbox\win\sandbox_poc\pocdll\registry.cc(24,10) :  note(clang): reinterpret_cast is not allowed in a constant expression

Since this function doesn't prevent any duplication, just kill
it and pass the string to Try() manually.

No behavior change.

BUG=82385
R=cpu@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293580}

Now that the new GN has landed with support for this, we can start using this flag.

R=viettrungluu@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293579}

BUG=411083
R=dbeam@chromium.org, stevenjb@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293578}

During teardown it's possible to race calling Renderer::GetMediaTime()
on the main thread with ~Renderer() on the media thread.

This was introduced in be9da705 by
moving the TimeDeltaInterpolator (which used to never get destroyed)
into Renderer (which does get destroyed during error/stop).

BUG=411320

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

Cr-Commit-Position: refs/heads/master@{#293577}

TBR=robertphilips@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293576}

FrameBuffer is basically a superset of FrameInfo, so let's merge FrameIdMap with Framer and
use FrameBuffer instead of FrameInfo.

No functional changes, only refactoring.

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

Cr-Commit-Position: refs/heads/master@{#293575}

There can be TabModels which know about Tabs that are not
alive and cannot yet be instantiated.  Do NULL checks before
checking the Tabs.

BUG=403592
R=dgozman@chromium.org, dtrainor@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293574}

It appears that RenderWidgetHostViewMac::Destroy is never getting
called in some instances, and that is resulting in crashes when we end
up in its destructor, which is called by Objective C's runtime.

I suspect that this is a leak somewhere, and that on other platforms we
simply never call the destructor.

Call the necessary bits of RenderWidgetHostViewMac::Destroy to avoid
crash when a RenderWidgetHostImpl reaches its destructor before its
view_ has been reset.

Also, turn the weak pointers to RenderWidgetHostViewBase in
RenderWidgetHostImpl and RenderWidgetHostViewGuest
to use base::WeakPtr to prevent the many dangling instances.

BUG=404828

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

Cr-Commit-Position: refs/heads/master@{#293573}

Followup of https://codereview.chromium.org/317093002/. This CL adds tests for showing confirmation dialog for unsecure signin.

As prerequisite, this CL also,

1. changes the signin continue url to a local page in the gaia auth extension.
2. adds LoginUiService::Observer events for showing signin confirmation dialog for unsecure signin.
3. fixes broken methods in FakeGaia

BUG=368905

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

Cr-Commit-Position: refs/heads/master@{#293572}

And validate them accordingly (all-space names are still empty and invalid).

BUG=405913
TEST=Go to chrome://settings. Try to enter "      " for the profile name. The
textbox should stay red. Enter "     batman    " for the profile name, and save.
The name should be saved as just "batman". Expect some bat signals.

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

Cr-Commit-Position: refs/heads/master@{#293571}

In the interest of phasing out the totally unnecessary
*Chrome*ExtensionFunction base classes, this establishes a
ChromeExtensionFunctionDetails object which can be created
by extension function implementations in //chrome who need
access to Chrome-specific details.

This object can be very easily composed into such function
implementations such that they can move away from using
e.g. ChromeAsyncExtensionFunction or
ChromeUIThreadExtensionFunction as a base class and instead
rely on more universal and generic ExtensionFunction and its
immediate derivatives.

A conversion of the tabs API ExecuteCodeInTabFunction is
included for demonstration purposes.

BUG=None
R=scheib@chromium.org
CC=lfg@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293570}

The DENIED judgement set by DenyCertForHost is never actually used to
make any interstitial decisions (it is, in fact, explicitly treated as
unknown). To simplify the API and make it cleaner, this change removes
DenyCertForHost from ssl_policy_backend.h and ssl_host_state_delegate.h
and the related classes.

BUG=402764

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

Cr-Commit-Position: refs/heads/master@{#293569}

Revert of Use SkSurface and SkImage instead of SkGpuDevice and SkBitmap in cc. (patchset #5 id:80001 of https://codereview.chromium.org/520793002/)

Reason for revert:
Looks like it may have broken the layout tests.

http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.7/builds/31264

Original issue's description:
> Use SkSurface and SkImage instead of SkGpuDevice and SkBitmap in cc.
>
> Committed: https://chromium.googlesource.com/chromium/src/+/37ffe8f81510bbfb82b48640aa96fe7e51efc654

TBR=enne@chromium.org,senorblanco@chromium.org,sugoi@chromium.org,danakj@chromium.org
NOTREECHECKS=true
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293568}

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

BUG=410611

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

Cr-Commit-Position: refs/heads/master@{#293567}

Switching the use_athena gyp-flag only affects the code inside //chrome. So move
the USE_ATHENA inside //chrome so that toggling the flag doesn't cause all
targets to be rebuilt, and only code inside //chrome is rebuilt instead. This
should also prevent accidental dependence on USE_ATHENA in code outside of
//chrome.

BUG=none
R=oshima@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293566}

I changed analyzer such that if a gyp file (or an included gypi file)
changes all targets in the gyp file are marked as changed. This means
I should no longer have to special case gyp files. I'm leaving the
exception in place for any gyp files in build as any change to those
really needs to recompile the world.

BUG=109173
TEST=none
R=thakis@chromium.org

Committed to pending queue: https://chromium.googlesource.com/chromium/src/+/5110e8b

Committed: https://chromium.googlesource.com/chromium/src/+/e53e29fc161f96871160f6db39919752a0376333

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

Cr-Commit-Position: refs/heads/master@{#293565}

It was rebased incorrectly and the new findbugs (from a move) weren't added.
BUG=398263
R=boliu@chromium.org
TBR=boliu

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

Cr-Commit-Position: refs/heads/master@{#293564}

BUG=None
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293563}

Previously, only BS/DEL set this guard but there are cases with keyboards
that send single characters immediately followed by a composition (e.g.
swiping words on stock Google keyboard) and we want to make sure that
there is no race condition where the actions taken in response to the
KeyPress don't cancel the following composition.

BUG=408678

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

Cr-Commit-Position: refs/heads/master@{#293562}

I recently added a test that uses pthread_t without including the pthread.h
header. This appears to be causing failures on the linux_arm_cross_compile bot.

BUG=394130

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

Cr-Commit-Position: refs/heads/master@{#293561}

Revert of [Ozone-GBM] Handle GPU crashes (patchset #4 id:60001 of https://codereview.chromium.org/522463005/)

Reason for revert:
boots to blank screen

Original issue's description:
> [Ozone-GBM] Handle GPU crashes
>
> If the GPU process crashes, all the display configuration state is gone.
> This allows the platform to gracefully handle GPU crashes and restore
> the state once the GPU process spins up again.
>
> BUG=none
> NOTRY=true
>
> Committed: https://chromium.googlesource.com/chromium/src/+/fe647532b9df0bfc9d0896fa3368b14ffca98936

TBR=alexst@chromium.org,kenrb@chromium.org,dnicoara@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=none

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

Cr-Commit-Position: refs/heads/master@{#293560}

TBR=cpu@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293559}

After implementing this optimization I found that it had no
impact on performance. Changing the TODO into a comment in
case we need to revisit this in the future.

BUG=
TBR=vmpstr
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293558}

password manager python tests.
Automatically wait for DOM element visibly at the beginning of
actions (click, submit) in the password manager python tests.

BUG=411325

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

Cr-Commit-Position: refs/heads/master@{#293557}

R=estade@chromium.org
BUG=407979
TEST=visual
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293556}

Reland: Issue 446203002: Initialize the now_function to the HighResNowWrapper in case High Res is supported

https://codereview.chromium.org/446203002/

The reland avoids using a static initializer for now_function, it initializes the function pointer on the first call instead.

I incorporated maruel@'s suggestions.

jam for
chrome/browser/
content/app/

willchan,maruel for
base/time/

BUG=400627
R=cpu@chromium.org, jam@chromium.org, maruel@chromium.org, thakis@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/a7c8e5e3411d6a3d32f4e1a61f8baa3e438fee52

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

Cr-Commit-Position: refs/heads/master@{#293555}

This change pulls in the following changes:

7bdec13 Export pqueue functions.
c92c2d7 Prune some dead quirks and document the SSL_OP_ALL ones.
859ec3c Add SSL_CTX_set_keylog_bio.
1f20799 Fix ARM build with OPENSSL_NO_ASM.
df90a64 Remove MD5, SHA-224, and SHA-512 handling from s3_cbc.c.
39ebf53 Check the server did not use a TLS 1.2 cipher suite pre-TLS 1.2.
120a674 Fix the return values for most of SRTP.
5c24a1d Add a test for SSL_OP_TLS_D5_BUG.
f852599 Fix doc.config for header files being moved.
f0fd373 Remove remnants of EVP_CIPHER-based AES_GCM cipher.
8a5825e Don't export obj_dat.h.
b2cb0ec Fix minor issues found by Clang's analysis.
ed8270a Fix crash as server when resuming with SNI.
04dbb7f Add tests for pqueue

BUG=none

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

Cr-Commit-Position: refs/heads/master@{#293554}

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

Cr-Commit-Position: refs/heads/master@{#293553}

Causing intermittent tab crashes, blocking CQ.

BUG=411372
TBR=skyostil@chromium.org
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293552}

There is a race condition in the way that match rules get set up for object
proxies created in response to GetManagedObjects that may cause us the miss
PropertiesChanged signals if they're received before the match rule and filter
function get added by ObjectProxy.

This patch changes this to work the "intended" way: ObjectManager now adds a
single match rule for its corresponding service name, and specifically for the
org.freedesktop.DBus.Properties.PropertiesChanged signal. Once it receives the
signal, ObjectManager dispatches the signal to the corresponding PropertySet.

BUG=407109,400768
TEST=dbus_unittests

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

Cr-Commit-Position: refs/heads/master@{#293551}