GitLab

The reason for removing these flags is because they seem to not be used, and they cause a problem in moving NaCl code to components, because they are defined in the chrome layer.

This is in preparation to move NaCl code to components.
BUG=244791

Review URL: https://chromiumcodereview.appspot.com/17041003

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

BUG=248160

Review URL: https://chromiumcodereview.appspot.com/16431010

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

TBR=dmichael@chromium.org
BUG=

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

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

Blink currently uses TEXTMETRICS for font metrics on windows,
regardless of the font type. Skia currently does not.

Set the SK_GDI_ALWAYS_USE_TEXTMETRICS_FOR_FONT_METRICS flag for
windows which will instruct Skia to use the same font metrics for the
GDI backend as our current GDI implementation.

BUG=252705
R=reed@google.com, thakis@chromium.org

Review URL: https://chromiumcodereview.appspot.com/17068009

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

- puts browser windows which would have used AppNonClientFrameViewAsh into maximized mode
- puts v1 app windows which would not have used AppNonClientFrameViewAsh and browser popup windows into tab fullscreen
- Makes Alt+ put windows into maximized mode. (That's what Ctrl+Alt+? indicates)

TEST=ChromeShellDelegateBrowserTest
BUG=251311

Review URL: https://chromiumcodereview.appspot.com/17515005

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

BUG=170401
TEST=unit tests
R=estade@chromium.org

Review URL: https://chromiumcodereview.appspot.com/16024018

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

BUG=none

Review URL: https://chromiumcodereview.appspot.com/17410009

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

This makes sync and net compile with no "using *Value".

BUG=

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

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

R=jam@chromium.org

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

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

BUG=237267
R=sky@chromium.org

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

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

BUG=232075

Review URL: https://chromiumcodereview.appspot.com/16749002

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

Because https://chromiumcodereview.appspot.com/17438002/ moved smoothness_measurement from perf_tools/ to measurements/.

BUG=None.
TEST=None.
R=tonyg@chromium.org

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

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

Also fix some pylint warnings.

BUG=none
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/17428004

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

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

This reverts r207892 - build failure on Linux x64.

TBR=kbr@chromium.org
BUG=238755

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

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

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

We do not desire to create an overlay that we never use.

BUG=247717
TBR=samarth@chromium.org

Review URL: https://chromiumcodereview.appspot.com/17413017

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

Try again w/ gyp fix.

TBR=kbr@chromium.org, mymax@amazon.com
BUG=238755

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

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

Broke Android Tests:
http://build.chromium.org/p/chromium.linux/buildstatus?builder=Android%20Tests&number=5462
Some output:
W  102s Main  Failed obtaining tests from 014E378305008009 with exception: End Of File (EOF) in read_nonblocking(). Exception style platform.
<pexpect.spawn object at 0x28d5510>
version: 2.3 ($Revision: 399 $)
command: /b/build_internal/scripts/slave/android/adb
args: ['/b/build_internal/scripts/slave/android/adb', '-s', '014E378305008009', 'shell', 'cat', '/data/data/org.chromium.native_test/files/test.fifo']
searcher: searcher_re:
    0: re.compile("<<ScopedMainEntryLogger")
buffer (last 100 chars): 
before (last 100 chars): t/browser/accessibility/BrowserAccessibilityManager

> Native Android accessibility.
> 
> This is the final changelist that completes the initial implementation.
> When accessibility is on and script injection is turned off or
> unavailable, constructs a BrowserAccessibilityManager for the
> ContentViewCore that provides a native accessibility implementation.
> 
> BUG=242953
> R=benm@chromium.org, bulach@chromium.org, dtrainor@chromium.org
> 
> Review URL: https://codereview.chromium.org/15741009

TBR=dmazzoni@chromium.org

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

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

BUG=249846
R=msw@chromium.org

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

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

This CL adds device policies that provide control over the default state
of the following four accessibility settings on the login screen:
* Large cursor
* Spoken feedback
* High contrast mode
* Screen magnifier type

The User can temporarily override the settings but the defaults are
restored whenever the login screen is shown anew or the user remains idle
on the login screen for one minute.

BUG=225955, 225956, 243350, 247298
TEST=New unittests + new browsertests + manual in VM

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

Review URL: https://chromiumcodereview.appspot.com/16658015

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

BUG=247548
R=gspencer@chromium.org

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

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

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

R=ronghuawu@chromium.org, wjia@chromium.org

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

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

It sent the wrong error code for duplicate SYN_REPLY frames. Also,
it didn't trigger an error for data frames sent before SYN_REPLY.

Update tests to match.

Add {Active,Pushed}StreamInfo structs and use them in
{Active,Pushed}StreamMap.

Be defensive when closing expired push streams.

Give the correct name to SpdyHttpStream tests.

BUG=252556
R=rch@chromium.org

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

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

Example use case is iterating on follow-up changes to a file changing
namespaces, impacting all the symbols within that file. 

R=joi

Review URL: https://chromiumcodereview.appspot.com/17527004

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

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

Noticed by Stuart.

BUG=251957
R=mark@chromium.org

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

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

This picks up a change which reverts the use-closest-match functionality
to find the closest match using ratio() instead of quick_ratio().

This fixes the ability to sign in to google accounts on Android which
fixes the smoothness_measurement.

Since ratio() is more expensive than quick_ratio(), it may also cause
the page cyclers to regress a little on all platforms. This is not a
chrome regression.

BUG=252786
NOTRY=True
TBR=slamm@google.com

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

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

TBR=dpranke

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

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

BUG=none
TBR=noelallen@chromium.org

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

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

Remove Nilesh while I'm here.

NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/17176026

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

This routes audio to speaker, instead of earpiece, by default for WebRTC on Android.

BUG=243506
TEST=run https://apprtc.appspot.com/?debug=loopback on Google Android devices. Audio will come out of speaker.
R=qinmin@chromium.org

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

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

This is the final changelist that completes the initial implementation.
When accessibility is on and script injection is turned off or
unavailable, constructs a BrowserAccessibilityManager for the
ContentViewCore that provides a native accessibility implementation.

BUG=242953
R=benm@chromium.org, bulach@chromium.org, dtrainor@chromium.org

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

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

- test.Test, which encapsulates a test and page set, and describes how to run it.
- test_runner, which runs test.Tests using a command-based CLI.

- benchmarks dir, which contains a list of test.Tests.
- run_measurement, which just calls test_runner.Main().

BUG=237412
TEST=None.
R=kbr@chromium.org, nduca@chromium.org, tonyg@chromium.org

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

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

BUG=249038
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/16950022

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

Change ShortcutsProvider so it can assign high relevance scores.
Simultaneously, make ShortcutsProvider explicitly enforce the rule
that it should not return a result with an inlineable score (>=1200).

Finally, create a field trial that will allow the server to specify
the maximum relevance score ShortcutsProvider can assign.  Setting this
to 1199 will maintain current behavior.  Also, if the field trial is
not enabled through the variations server, Chrome will maintain the
current behavior.

BUG=252032
TEST=enter omnibox inputs that you've used before to get places (and hence shortcuts will have data about them) into about:omnibox and look at the resulting scores.  Try again with --force-fieldtrials=OmniboxShortcutsScoring/MaxRelevance_XXX/ (where XXX is a number) and see how the scores change.

Review URL: https://chromiumcodereview.appspot.com/17261012

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

Minor cleanup to remove the static thread-safe methods on BrowserMainLoop. Initially I thought this would be one getter so it seemed fine, but now it has 3 and more are on the way. Switch to one static getter for this class, and then getters for the member variables. I used dependency injection to allow access to these objects from other threads, which also cleaned up tests a bit.

R=scherkus@chromium.org

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

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

Basically three new file block types appear: One for normal
entries, one for deleted entries and one for keeping track
of external files.

BUG=241277
TEST=net_unittests
R=gavinp@chromium.org

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

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

Resolves the issue of using a plugin installed through an extension in
more than one profile.

BUG=132894
TEST=Install an extension with plugin in two profiles and observe it works (e.g. Legacy Browser Support)

Review URL: https://chromiumcodereview.appspot.com/17543004

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