Replace third_party/WebKit with third_party/blink in *.md

Also, apply snake_case to file basenames.

[email protected]

Bug: 768828
Change-Id: I28bead32daf1adbf15033b778c633b034a743562
Reviewed-on: https://chromium-review.googlesource.com/1001436
Reviewed-by: Kent Tamura <[email protected]>
Commit-Queue: Kent Tamura <[email protected]>
Cr-Commit-Position: refs/heads/master@{#549110}

cc/animation/README.md

@@ -157,5 +157,5 @@ base. [Smooth Scrolling in Chromium](https://goo.gl/XXwAwk) provides
 an overview of smooth scrolling. There is further class header
 documentation in
 Blink's
-[platform/scroll](https://codesearch.chromium.org/chromium/src/third_party/WebKit/Source/platform/scroll/)
+[platform/scroll](https://codesearch.chromium.org/chromium/src/third_party/blink/renderer/platform/scroll/)
 directory.

content/browser/bluetooth/README.md

@@ -7,7 +7,7 @@ This service is exposed to the web in the [blink bluetooth module].
 
 [Web Bluetooth specification]: https://webbluetoothcg.github.io/web-bluetooth/
 [/device/bluetooth]: /device/bluetooth
-[blink bluetooth module]: /third_party/WebKit/Source/modules/bluetooth/
+[blink bluetooth module]: /third_party/blink/renderer/modules/bluetooth/
 
 
 ## Testing

content/browser/download/docs/save-page-as.md

@@ -130,11 +130,11 @@ Pointers to related code outside of `//content/browser/download`:
     * `//content/renderer/savable_resources...`
 
 * Blink:
-    * `//third_party/WebKit/public/web/WebFrameSerializer...`
-    * `//third_party/WebKit/Source/web/WebFrameSerializerImpl...`
+    * `//third_party/blink/public/web/web_frame_serializer...`
+    * `//third_party/blink/renderere/core/frame/web_frame_serializer_impl...`
       (used for Complete HTML today;  should use `FrameSerializer` instead in
       the long-term - see https://crbug.com/328354).
-    * `//third_party/WebKit/Source/core/frame/FrameSerializer...`
+    * `//third_party/blink/renderer/core/frame/frame_serializer...`
       (used for MHTML today)
-    * `//third_party/WebKit/Source/platform/mhtml/MHTMLArchive...`
+    * `//third_party/blink/renderer/platform/mhtml/mhtml_archive...`
 

device/bluetooth/test/README.md

@@ -6,7 +6,7 @@ the Bluetooth component.
 There are also notable higher level bluetooth tests:
 
 *   [Extensions](/extensions/browser/api/bluetooth/)
-*   [Web Bluetooth](/third_party/WebKit/Source/modules/bluetooth/README.md)
+*   [Web Bluetooth](/third_party/blink/renderer/modules/bluetooth/README.md)
 
 
 ## Client Testing

docs/accessibility/overview.md

@@ -510,23 +510,23 @@ is defined by [automation.idl], which must be kept synchronized with
 [AccessibilityHostMsg_EventParams]: https://cs.chromium.org/chromium/src/content/common/accessibility_messages.h?sq=package:chromium&l=75
 [AutomationInternalCustomBindings]: https://cs.chromium.org/chromium/src/chrome/renderer/extensions/automation_internal_custom_bindings.h
 [AXContentNodeData]: https://cs.chromium.org/chromium/src/content/common/ax_content_node_data.h
-[AXLayoutObject]: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.h
-[AXNodeObject]: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/modules/accessibility/AXNodeObject.h
-[AXObjectImpl]: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/modules/accessibility/AXObjectImpl.h
-[AXObjectCacheImpl]: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/modules/accessibility/AXObjectCacheImpl.h
+[AXLayoutObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_layout_object.h
+[AXNodeObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_node_object.h
+[AXObjectImpl]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_object_impl.h
+[AXObjectCacheImpl]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_object_cache_impl.h
 [AXPlatformNode]: https://cs.chromium.org/chromium/src/ui/accessibility/platform/ax_platform_node.h
 [AXTreeSerializer]: https://cs.chromium.org/chromium/src/ui/accessibility/ax_tree_serializer.h
 [BlinkAXTreeSource]: https://cs.chromium.org/chromium/src/content/renderer/accessibility/blink_ax_tree_source.h
 [BrowserAccessibility]: https://cs.chromium.org/chromium/src/content/browser/accessibility/browser_accessibility.h
 [BrowserAccessibilityDelegate]: https://cs.chromium.org/chromium/src/content/browser/accessibility/browser_accessibility_manager.h?sq=package:chromium&l=64
 [BrowserAccessibilityManager]: https://cs.chromium.org/chromium/src/content/browser/accessibility/browser_accessibility_manager.h
-[LayoutObject]: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/layout/LayoutObject.h
+[LayoutObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/layout/layout_object.h
 [NativeViewAccessibility]: https://cs.chromium.org/chromium/src/ui/views/accessibility/native_view_accessibility.h
-[Node]: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/Node.h
+[Node]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/dom/Node.h
 [RenderAccessibilityImpl]: https://cs.chromium.org/chromium/src/content/renderer/accessibility/render_accessibility_impl.h
 [RenderFrameHostImpl]: https://cs.chromium.org/chromium/src/content/browser/frame_host/render_frame_host_impl.h
 [ui::AXNodeData]: https://cs.chromium.org/chromium/src/ui/accessibility/ax_node_data.h
-[WebAXObject]: https://cs.chromium.org/chromium/src/third_party/WebKit/public/web/WebAXObject.h
+[WebAXObject]: https://cs.chromium.org/chromium/src/third_party/blink/public/web/web_ax_object.h
 [automation API]: https://cs.chromium.org/chromium/src/chrome/renderer/resources/extensions/automation
 [automation.idl]: https://cs.chromium.org/chromium/src/chrome/common/extensions/api/automation.idl
 [ax_enums.idl]: https://cs.chromium.org/chromium/src/ui/accessibility/ax_enums.idl

docs/chromoting_android_hacking.md

@@ -79,8 +79,8 @@ display log messages to the `LogCat` pane.
 <classpathentry kind="src" path="remoting/android/java/src"/>
 <classpathentry kind="src" path="remoting/android/apk/src"/>
 <classpathentry kind="src" path="remoting/android/javatests/src"/>
-<classpathentry kind="src" path="third_party/WebKit/Source/devtools/scripts/jsdoc-validator/src"/>
-<classpathentry kind="src" path="third_party/WebKit/Source/devtools/scripts/compiler-runner/src"/>
+<classpathentry kind="src" path="third_party/blink/renderer/devtools/scripts/jsdoc-validator/src"/>
+<classpathentry kind="src" path="third_party/blink/renderer/devtools/scripts/compiler-runner/src"/>
 <classpathentry kind="src" path="third_party/webrtc/voice_engine/test/android/android_test/src"/>
 <classpathentry kind="src" path="third_party/webrtc/modules/video_capture/android/java/src"/>
 <classpathentry kind="src" path="third_party/webrtc/modules/video_render/android/java/src"/>

docs/how_to_add_your_feature_flag.md

@@ -22,11 +22,11 @@ to see
 [[1](https://chromium-review.googlesource.com/c/554510/8/content/common/service_worker/service_worker_utils.cc#153)]
 3. how to wire the base::Feature to WebRuntimeFeatures
 [[1](https://chromium-review.googlesource.com/c/554510/8/content/child/runtime_features.cc)]
-[[2](https://chromium-review.googlesource.com/c/554510/8/third_party/WebKit/public/platform/WebRuntimeFeatures.h)]
-[[3](https://chromium-review.googlesource.com/c/554510/third_party/WebKit/Source/platform/exported/WebRuntimeFeatures.cpp)]
-[[4](https://chromium-review.googlesource.com/c/554510/8/third_party/WebKit/Source/platform/runtime_enabled_features.json5)]
+[[2](https://chromium-review.googlesource.com/c/554510/8/third_party/blink/public/platform/web_runtime_features.h)]
+[[3](https://chromium-review.googlesource.com/c/554510/third_party/blink/Source/platform/exported/web_runtime_features.cc)]
+[[4](https://chromium-review.googlesource.com/c/554510/8/third_party/blink/renderer/platform/runtime_enabled_features.json5)]
 4. how to use it in blink
-[[1](https://chromium-review.googlesource.com/c/554510/8/third_party/WebKit/Source/core/workers/WorkerThread.cpp)]
+[[1](https://chromium-review.googlesource.com/c/554510/8/third_party/blnk/renderere/core/workers/worker_thread.cc)]
 
 Also, this patch added a virtual test for running layout tests with the flag.
 When you add a flag, you can consider to use that.

docs/memory-infra/README.md

@@ -91,7 +91,7 @@ and it is discounted from malloc and the blue columns.
 
 <!-- TODO(primiano): Improve this. https://crbug.com/??? -->
 
-[oilpan]:     /third_party/WebKit/Source/platform/heap/BlinkGCDesign.md
+[oilpan]:     /third_party/blink/renderer/platform/heap/BlinkGCDesign.md
 [discardable]:base/memory/discardable_memory.h
 [cc-memory]:  probe-cc.md
 [gpu-memory]: probe-gpu.md

docs/origin_trials_integration.md

@@ -134,7 +134,7 @@ as tests for script-added tokens. For examples, refer to the existing tests in
 [chrome_origin_trial_policy.cc]: /chrome/common/origin_trials/chrome_origin_trial_policy.cc
 [generate_token.py]: /tools/origin_trials/generate_token.py
 [Developer Guide]: https://github.com/jpchase/OriginTrials/blob/gh-pages/developer-guide.md
-[OriginTrialEnabled]: /third_party/WebKit/Source/bindings/IDLExtendedAttributes.md#_OriginTrialEnabled_i_m_a_c_
+[OriginTrialEnabled]: /third_party/blink/renderer/bindings/IDLExtendedAttributes.md#_OriginTrialEnabled_i_m_a_c_
 [origin_trials/webexposed]: /third_party/WebKit/LayoutTests/http/tests/origin_trials/webexposed/
-[runtime\_enabled\_features.json5]: /third_party/WebKit/Source/platform/runtime_enabled_features.json5
+[runtime\_enabled\_features.json5]: /third_party/blink/renderer/platform/runtime_enabled_features.json5
 [trial_token_unittest.cc]: /content/common/origin_trials/trial_token_unittest.cc

docs/testing/writing_layout_tests.md

@@ -21,7 +21,7 @@ Layout tests should be used to accomplish one of the following goals:
    get better. This is very much in line with our goal to move the Web forward.
 2. When a Blink feature cannot be tested using the tools provided by WPT, and
    cannot be easily covered by
-   [C++ unit tests](https://cs.chromium.org/chromium/src/third_party/WebKit/Source/web/tests/?q=webframetest&sq=package:chromium&type=cs),
+   [C++ unit tests](https://cs.chromium.org/chromium/src/third_party/blink/renderer/web/tests/?q=webframetest&sq=package:chromium&type=cs),
    the feature must be covered by layout tests, to avoid unexpected regressions.
    These tests will use Blink-specific testing APIs that are only available in
    [content_shell](./layout_tests_in_content_shell.md).

mojo/README.md

@@ -67,7 +67,7 @@ wrapping and unwrapping helpers, common handle operations, and utilities for
 more easily watching handle state changes.
 
 ### JavaScript
-The [**JavaScript System API**](/third_party/WebKit/Source/core/mojo) exposes
+The [**JavaScript System API**](/third_party/blink/renderer/core/mojo) exposes
 the Mojo primitives to JavaScript, covering all basic functionality of the
 low-level C API.
 

services/device/generic_sensor/README.md

@@ -9,7 +9,7 @@ Sensors Mojo interfaces are defined in the `services/device/public/mojom` subdir
 
 ### [Generic Sensors](https://www.w3.org/TR/generic-sensor/)
 
-The Generic Sensors API is implemented in `third_party/WebKit/Source/modules/sensor` and exposes the following sensor types as JavaScript objects:
+The Generic Sensors API is implemented in `third_party/blink/renderer/modules/sensor` and exposes the following sensor types as JavaScript objects:
 
 * [AbsoluteOrientationSensor] → ABSOLUTE_ORIENTATION_QUATERNION
 * [Accelerometer] → ACCELEROMETER
@@ -19,17 +19,17 @@ The Generic Sensors API is implemented in `third_party/WebKit/Source/modules/sen
 * [Magnetometer] → MAGNETOMETER
 * [RelativeOrientationSensor] → RELATIVE_ORIENTATION_QUATERNION
 
-[AbsoluteOrientationSensor]: ../../../third_party/WebKit/Source/modules/sensor/AbsoluteOrientationSensor.idl
-[Accelerometer]: ../../../third_party/WebKit/Source/modules/sensor/Accelerometer.idl
-[AmbientLightSensor]: ../../../third_party/WebKit/Source/modules/sensor/AmbientLightSensor.idl
-[Gyroscope]: ../../../third_party/WebKit/Source/modules/sensor/Gyroscope.idl
-[LinearAccelerationSensor]: ../../../third_party/WebKit/Source/modules/sensor/LinearAccelerationSensor.idl
-[Magnetometer]: ../../../third_party/WebKit/Source/modules/sensor/Magnetometer.idl
-[RelativeOrientationSensor]: ../../../third_party/WebKit/Source/modules/sensor/RelativeOrientationSensor.idl
+[AbsoluteOrientationSensor]: ../../../third_party/blink/renderer/modules/sensor/absolute_orientation_sensor.idl
+[Accelerometer]: ../../../third_party/blink/renderer/modules/sensor/accelerometer.idl
+[AmbientLightSensor]: ../../../third_party/blink/renderer/modules/sensor/ambient_light_sensor.idl
+[Gyroscope]: ../../../third_party/blink/renderer/modules/sensor/gyroscope.idl
+[LinearAccelerationSensor]: ../../../third_party/blink/renderer/modules/sensor/linear_acceleration_sensor.idl
+[Magnetometer]: ../../../third_party/blink/renderer/modules/sensor/magnetometer.idl
+[RelativeOrientationSensor]: ../../../third_party/blink/renderer/modules/sensor/relative_orientation_sensor.idl
 
 ### [DeviceOrientation Events](https://www.w3.org/TR/orientation-event/)
 
-The DeviceOrientation Events API is implemented in `third_party/WebKit/Source/modules/device_orientation` and exposes two events based on the following sensors:
+The DeviceOrientation Events API is implemented in `third_party/blink/renderer/modules/device_orientation` and exposes two events based on the following sensors:
 
 * [DeviceMotionEvent]
   * ACCELEROMETER: populates the `accelerationIncludingGravity` field
@@ -39,8 +39,8 @@ The DeviceOrientation Events API is implemented in `third_party/WebKit/Source/mo
   * ABSOLUTE_ORIENTATION_EULER_ANGLES (when a listener for the `'deviceorientationabsolute'` event is added)
   * RELATIVE_ORIENTATION_EULER_ANGLES (when a listener for the `'deviceorientation'` event is added)
 
-[DeviceMotionEvent]: ../../../third_party/WebKit/Source/modules/device_orientation/DeviceMotionEvent.idl
-[DeviceOrientationEvent]: ../../../third_party/WebKit/Source/modules/device_orientation/DeviceOrientationEvent.idl
+[DeviceMotionEvent]: ../../../third_party/blink/renderer/modules/device_orientation/device_motion_event.idl
+[DeviceOrientationEvent]: ../../../third_party/blink/renderer/modules/device_orientation/device_orientation_event.idl
 
 The content renderer layer is located in `content/renderer/device_sensors`.
 

third_party/blink/common/README.md

@@ -3,24 +3,19 @@
 This directory contains the common Web Platform stuff that needs to be shared
 by renderer-side and browser-side code.
 
-Things that live in `third_party/WebKit` can directly depend on this directory,
-while the code outside the WebKit directory (e.g. `//content` and `//chrome`)
+Things that live in `third_party/blink` can directly depend on this directory,
+while the code outside the Blink directory (e.g. `//content` and `//chrome`)
 can only depend on the common stuff via the public headers exposed in
-`WebKit/public/common`.
+`blink/public/common`.
 
 Anything in this directory should **NOT** depend on the non-common stuff
-in the WebKit directory. See `DEPS` and `BUILD.gn` files for more details.
+in the Blink directory. See `DEPS` and `BUILD.gn` files for more details.
 
 Code in this directory would normally use `blink` namespace.
 
-Unlike other directories in WebKit, code in this directory should:
+Unlike other directories in Blink, code in this directory should:
 
 * Use Chromium's common types (e.g. //base ones) rather than Blink's ones
   (e.g. WTF types)
 
-* Use underscore_separated_file_names.cc style rather than CamelCase.cpp.
-
 * Follow [Chromium's common coding style guide](https://chromium.googlesource.com/chromium/src/+/master/styleguide/c++/c++.md)
-
-* Use full-path from src/ for includes (e.g. `third_party/WebKit/common/foo.h`
-  rather than `common/foo.h`).

third_party/blink/common/feature_policy/README.md

@@ -4,7 +4,7 @@
 Feature policy (see [spec](https://wicg.github.io/feature-policy/)) is a
 mechanism that allows developers to selectively enable and disable various
 [browser features and
-APIs](https://cs.chromium.org/chromium/src/third_party/WebKit/public/mojom/feature_policy/feature_policy.mojom)
+APIs](https://cs.chromium.org/chromium/src/third_party/blink/public/mojom/feature_policy/feature_policy.mojom)
 (e.g, "vibrate", "fullscreen", "usb", etc.). A feature policy can be defined
 via a HTTP header and/or an iframe "allow" attribute.
 
@@ -51,17 +51,17 @@ policy is undetermined, consider shipping the feature behind a flag (i.e.,
 
 ##### Define new feature
 1. Feature policy features are defined in
-`third_party/WebKit/public/common/feature_policy/feature_policy_feature.h`. Add the new feature
+`third_party/blink/public/common/feature_policy/feature_policy_feature.h`. Add the new feature
 enum with a brief decription about what the feature does in the comment, right
 above `LAST_FEATURE`
 
 2. Append the new feature enum with a brief description as well in
-`third_party/WebKit/public/mojom/feature_policy/feature_policy.mojom`
+`third_party/blink/public/mojom/feature_policy/feature_policy.mojom`
 
-3. Update `third_party/WebKit/public/mojom/feature_policy/feature_policy.mojom_traits.h`
+3. Update `third_party/blink/public/mojom/feature_policy/feature_policy.mojom_traits.h`
 to include the new feature
 
-4. Update `third_party/WebKit/Source/platform/feature_policy/FeaturePolicy.cpp`:
+4. Update `third_party/blink/renderer/platform/feature_policy/feature_policy.cc`:
 Add your `("feature-name", FeatureEnumValue)` mapping to
   `GetDefaultFeatureNameMap()` (note: "feature-name" is the string web
   developers will be using to define the policy in the HTTP header and iframe