GitLab

Adds Java version of DomDistillerService and 
DistilledPagePrefs with support for setting and retrieving
the current Theme.

The DomDistillerService can be retrieved by using the
DomDistillerServiceFactory, which maps a profile to an
instance of the service.

BUG=383630

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

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

Wrapper class is currently located in the unittest file and is a friend of touch_exploration_controller.

BUG=377040

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

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

Removing the include of Xlib.h makes selection_requestor.h more easily
testable. In particular, the definition of None in X.h conflicts with
that in gtest-type-util.h

This CL also adds XAtom to x11_types.h so that it does not need to be forward declared everywhere.

BUG=None
TEST=None
R=derat,danakj
TBR=dcheng (for trivial change to clipboard_aurax11.cc)

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

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

This also fixes the naming of several existing IDs.

BUG=365411

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

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

BUG=None
NOTRY=True

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

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

BUG=346958

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

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

Where it reads = it should read |= so it keep the blacklisting mark.

TBR=tommi@chromium.org

BUG=347371

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

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

> deep_memory_profiler: Replace 'WebCore' with 'blink'.
> 
> TBR=abarth@chromium.org
> 
> Review URL: https://codereview.chromium.org/400563003

TBR=mkwst@chromium.org

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

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

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

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

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

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

File paths can be very slow to access because finding a file by path requires
O(N) metadata access to figure out which file id corresponds to a given name.

BUG=385307

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

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

BUG=267773

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

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

Also, remove the profile service that was only used by the network
service because it couldn't access the path service on android.

R=darin@chromium.org

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

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

SelectiveAck was over confirming due to unsigned in misuse. This adds a test
that exercises the confirm logic used by SelectiveAck.

BUG=392664

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

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

Unlike the other kinds of errors which are detected earlier in navigation
(SSL certs, etc), when the Blink reflected XSS filter encounters an
XSS and the page needs to be blocked (per the server's request), we 
already are have a commited navigation, and are well past the point
where interstitials and the like would do us any good.

Consequently, blink just aborts the load, and schedules a navigation to
data:, with history replacement enabled, so that the offending entry
is lost (note https://codereview.chromium.org/301163006/ changes this
behaviour blink-side to add to the back-forward list).

This is less than ideal when a webmaster would like to do a view-source on
the offending page so as to diagnose the cause, so what I've done is to set
up a way to flag the offending entry when the reflection is detected. 
I'd really like to just continue with navigating to data:, rather than
trying to deal with the UX issue -- there's nothing to be done, and 
screaming about XSS isn't helpful to the user -- and we aren't going
to ever add a "revisit the page with protection disabled" option neither.

So, when a block is detected, we make an IPC call to flag the current entry
in the navigation controller.  The navigation then continues to data:,. 

When we encounter a view-source on the data:, page URL, we check if the 
previous page was explicitly flagged prior to the block. If so, show its
source instead.

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

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

This is a follow up of https://codereview.chromium.org/392063002/

BUG=none
TBR=viettrungluu@chromium.org
TEST=none

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

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

Create a separate RenderWidgetResizeHelper to handle intercepting 
and early-processing of IPCs that need to be run during an active 
resize. This functionality was previously handled in 
RenderWidgetHelper. 

The only functional changes made to RenderWidgetResizeHelper during 
its excision is that it is a single global structure, as compared with
the per-RenderProcessImpl RenderWidgetHelper. It will execute any IPCs
from any renderer or the GPU processes that are forwarded to it. This is
preferable, as that makes it so that live resize in one window does 
not destroy performance in other windows. 

Because RenderWidgetResizeHelper can handle GPU process IPCs, we can 
tear out the bizarre behavior where we'd translate GPU IPCs to synthetic 
renderer IPCs get them to channel through RenderWidgetHelper (this is 
all of the deleted ViewHostMsg_CompositorSurfaceBuffersSwapped code). 

Mark this entire structure as Mac-only, and put it in Mac-only files,
since it doesn't get used on other platforms.

Future changes will make RenderWidgetResizeHelper have a TaskRunner, 
which we will pass to the compositor, so that we can pump new frames 
while inside -[RenderWidgetHostViewMac setFrameSize:].

BUG=392031

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

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

TBR=abarth@chromium.org

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

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

This CL brought to you by the commands 'grep', 'xargs', and 'sed'.

    grep -r -l "WebCore" ./tools/valgrind | xargs -L1 sed -i '' -e 's/WebCore/blink/g'
TBR=abarth@chromium.org

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

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

It turns out that on some OEM devices the Files app is placed near the
end, so placing the OEM folder before the last non-removable app does
not have the desired result.

Instead, we place it after the WebStore, and assume that a pre-installed
app (e.g. Search) exists so that the app location is stable.

This was tested succesfully on an official build on one of the failing
devices. (I also confirmed that all of the existing defailt_app_order
files have the WebStore followed by Search early in the list).

BUG=chrome-os-partner:29764

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

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

Pass CONFIGURATION_NAME as an argument to pack_arm_relocations.py, and
turn on packing only if its value is 'Release'.  (CONFIGURATION_NAME
cannot be used in conditionals because it is not resolved until after
the conditional has been processed.)

Prior art:
  https://code.google.com/p/chromium/codesearch#chromium/src/build/android/gyp/apk_obfuscate.py&l=103
  https://code.google.com/p/chromium/codesearch#chromium/src/build/java_apk.gypi&l=742

BUG=385553

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

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

TBR=abarth@chromium.org

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

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

The CL do:

* Remove the device rect argument from paintDeviceRect because the rectangle can
be calculated from other arguments.

* Remove setByFrame(AndFit) helper functions that are used only once each to simplify
the Viewport class.

* Rename getScreenClipped with getImageBoundsOnScreenClipped. The old name
  sounds it retuns the bounds of screen.

* Add getImageElementBounds to obtain the bounds before applying zoom and
  offset.

BUG=245926
TEST=manually

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

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

This should fix ASan CHECK failures when a report happens after Chrome used DbgHelp once
BUG=394220,345874
TBR=rnk@chromium.org
NOTRY=true

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

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

iBUG=308426

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

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

Bug was introduced in r283303.

BUG=383630

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

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

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

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

BUG=None
TEST=Peter is happy
TBR=erg

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

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

BUG=349211
TEST=Existing tests pass.

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

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

Retry downloading rules after 8, 16, 32, 64, 128, 256, and 512 seconds,
while requestAutocomplete dialog is open. (512 seconds is ~8.5 minutes.)

TEST=libaddressinput_unittests:FailingAddressValidatorTest.*
BUG=343397

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

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

The tests verify that FileTaskExecutor indeed performs the intended
interaction with the Drive file system and the remote server to obtain
an authenticated URL, and tries to open the link.

BUG=161209

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

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

In the GLHelper unittest the ValidateScalerStages function checks that
the scaling stages to be executed for the scale are valid.

This change also adds a check to ensure that the size of the destination
texture matches the destination size in the last stage of the scaler
pipeline.

This identified some of the test cases had small errors in the
destination sizes which didn't match the description of the scale. The
patch also corrects those.

TEST=content_gl_tests passes
BUG=None

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

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

The test was disabled[1] when XMLHttpRequest forbidden header names changed[2].
This CL updates and enables it.

1: https://src.chromium.org/viewvc/chrome?view=rev&revision=282507
2: https://src.chromium.org/viewvc/blink?view=rev&revision=178023

BUG=373120

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

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

The previous location of Start/StopTest isn't correct because it does
not encompass all calls to
AddSkip/AddSuccess/AddFailure/etc. Unfortunately, the new location 
means that test with discard_first_result will still execute
StartTest/StopTest. I think this is fine.

Also add Start/StopTest around the check for test.CanRunForPage(page)
for the same reason.

BUG=392901

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

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

There is a same-origin check in
ServiceWorkerContainer::registerServiceWorker, so this code should
only be reachable if something has gone wrong.

BUG=394213

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

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

BUG=392280
TEST=built with chromeos==1 use_ozone==1 & ran with egltest platform

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

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

BUG=347425
TEST=./unit_tests --gtest_filter="MetadataDatabase*"

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

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

TBR=dmazzoni@chromium.org

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

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

Use the window's bounds if available instead of restore bounds for the initial size of the restored web contents.

BUG=378924

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

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

Much of this change is search-and-replace RenderView-->RenderFrame and
render_view_id-->render_frame_id.  However, the following significant
changes have also been made, mainly to simplify/clarify/clean-up the
same LOC that would have had to be changed anyway:

1. Desktop and Tab capture APIs now "register" a WebContents instance,
   rather than a RenderViewHost.  This is a more-appropriate choice than
   registering a RenderFrameHost, and simplifies a lot of code.
2. Removed unnecessary "prepending" and "stripping" of the first part of
   the tab capture device ID in special circumstances.  It is no longer
   necessary.
3. TabCaptureRegistry uses WebContentsObserver to detect all fullscreen
   changes, rather than the deprecated NotificationObserver scheme.
4. Fixes for buggy MediaStreamImpl tear-down: MediaStreamDispatcher is
   now explicitly owned by MediaStreamImpl, to ensure it is destroyed
   only after it is no longer needed.  Also, weak pointers to
   MediaStreamImpl are invalidated before MSI data members are destroyed
   (it was observed during testing that outstanding callbacks were
   firing *after* the data members were destroyed).

Testing:

1. All relevant content_unittests and browser_tests run.
2. Manually engaged tab capture and desktop capture using Google Cast
   extension and "Desktop Capture Example"
   (https://developer.chrome.com/extensions/samples) to test screen
   picker UI.
3. Ran WebRTC demo: http://apprtc.appspot.com
4. Confirmed Flash webcam and microphone input.
5. Checked tab capture/recording/audio indicators.
6. Confirmed HTML5 and Flash fullscreen-within-tab functionality during
   tab capture.

BUG=304341,323223,320200,163100,338445
TEST=See "Testing" above.
TBR=kenrb@chromium.org

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

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