Add support for *BSD where necessary, equivalent to what Linux does.

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250026 0039d316-1c4b-4281-b951-d872f2087c98
Blink roll 166755:166772

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=166756:166772&mode=html
TBR=
BUG=

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250028 0039d316-1c4b-4281-b951-d872f2087c98
Clean up ui_resources to only include necessary resources.

BUG=326023

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250029 0039d316-1c4b-4281-b951-d872f2087c98
events: Remove no-op events.

No-op events were used only in a test to terminate a message-loop. So remove
the no-op events related code from the API, and directly terminate the message
loop in the test instead.

BUG=none
R=oshima@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250030 0039d316-1c4b-4281-b951-d872f2087c98
Revert of Split preserve3d into: "should-flatten" and "is-3d-sorted" (https://codereview.chromium.org/147833003/)

Reason for revert:
Introduces flakiness in Blink layout tests:

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%2540ToT%2520Blink&tests=compositing%252Fbackface-visibility-transformed

Original issue's description:
> Split preserve3d into: "should-flatten" and "is-3d-sorted"
> 
> Preserve3d has implications for both sorting and flattening of
> transforms. This is a bummer. Sometimes we want to allow a transform to
> remain unflattened, but we don't want that to affect 3d sorting. With
> this CL, we will have the ability to do that.
> 
> Note: this is essentially this cl
> https://codereview.chromium.org/100393005/
> 
> ..minus the generalizations to sorting that were being attempted in that
> patch.
> 
> Note, this CL is gated on https://codereview.chromium.org/98373011/ 
> 
> R=enne@chromium.org
> BUG=338980
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=249974

TBR=enne@chromium.org,shawnsingh@chromium.org,vollick@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=338980

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250031 0039d316-1c4b-4281-b951-d872f2087c98
Trigger the bots using the build/whitespace_file.txt to retry iOS Device
bot which is red.

TBR=skobes@chromium.org
NOTREECHECKS=true
BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250034 0039d316-1c4b-4281-b951-d872f2087c98
android: Require exe unittests to have a foo_unittest_stripped target.

This allows the test runner to not depend on the STRIP env var, which is going away.

Other approaches considered:
1. Converting the remaining exe-based tests to apk tests. The apk versions
   were slower, and didn't pass without other changes though.
2. Just don't strip. But that slows down these two tests by over 100%
   (due to copying data to the device is slow, and stripped size is 0.5MB while
   unstripped size is on the order of 10MB).
3. Try to get a trip binary from third_party/android_tools/ndk. That's fiddly
   since it requires getting the right arch.

Since there are only two exe-based tests left, just strip them from gyp.
Medium-term, maybe gyp/mac's postbuild stuff can be brought to android,
it looks like there are various things that could be made simpler with that.

BUG=142642
TEST=
build/android/test_runner.py gtest -s sandbox_linux_unittests &&
build/android/test_runner.py gtest -s breakpad_unittests

R=bulach@chromium.org, frankf@chromium.org
TBR=jln, thestig

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

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