Index: third_party/WebKit/Source/core/inspector/browser_protocol.json |
diff --git a/third_party/WebKit/Source/core/inspector/browser_protocol.json b/third_party/WebKit/Source/core/inspector/browser_protocol.json |
index cf7c9d0d2ef540953d515c60dab978c5a55f5e6f..deac5471445b24e39e8a92987dcfa285e1da3e95 100644 |
--- a/third_party/WebKit/Source/core/inspector/browser_protocol.json |
+++ b/third_party/WebKit/Source/core/inspector/browser_protocol.json |
@@ -747,6 +747,21 @@ |
"handlers": ["browser"] |
}, |
{ |
+ "name": "setVisualTransformOverride", |
dgozman
2016/08/18 20:11:10
The overall approach sounds good, but I think we s
Eric Seckler
2016/08/18 22:04:28
Hmm, the current parameters in the device metrics
|
+ "description": "Overrides the visible area of the page in the frame. In effect, moves the specified area of the page into the top-left corner of the frame.", |
+ "parameters": [ |
+ { "name": "x", "type": "number", "description": "X coordinate of top-left corner of the area (CSS pixels)." }, |
+ { "name": "y", "type": "number", "description": "Y coordinate of top-left corner of the area (CSS pixels)." }, |
+ { "name": "width", "type": "number", "description": "Width of the area (CSS pixels)." }, |
dgozman
2016/08/18 20:11:10
So, these are here only for optimization purpose?
Eric Seckler
2016/08/18 22:04:28
We only use them to specify the interest area for
|
+ { "name": "height", "type": "number", "description": "Height of the area (CSS pixels)." }, |
+ { "name": "scale", "type": "number", "optional": true, "description": "Scale to apply to the selected area (default 1.0)." } |
+ ] |
+ }, |
+ { |
+ "name": "clearVisualTransformOverride", |
+ "description": "Clears any active visual transform override." |
+ }, |
+ { |
"name": "resetPageScaleFactor", |
"description": "Requests that page scale factor is reset to initial values." |
}, |