Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(830)

Unified Diff: sky/specs/ui.md

Issue 772713002: Specs: markdown cleanup (Closed) Base URL: https://github.com/domokit/mojo.git@master
Patch Set: Created 6 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: sky/specs/ui.md
diff --git a/sky/specs/ui.md b/sky/specs/ui.md
index 2914f0cf459f838fe59c5cc2f249d80ed00f3fc7..fc67ddebeb3b538e262b54ef9e7b4e60a1a35631 100644
--- a/sky/specs/ui.md
+++ b/sky/specs/ui.md
@@ -92,134 +92,135 @@ pointer.
These events all bubble and their data is an object with the following
fields:
- pointer: an integer assigned to this touch or pointer when it
- enters the system, never reused, increasing
- monotonically every time a new value is assigned,
- starting from 1 (if the system gets a new tap every
- microsecond, this will cause a problem after 285 years)
-
- kind: one of 'touch', 'mouse', 'stylus', 'inverted-stylus'
-
- x: x-position relative to the top-left corner of the
- surface of the node on which the event was fired
-
- y: y-position relative to the top-left corner of the
- surface of the node on which the event was fired
-
- buttons: a bitfield of the buttons pressed, from the following
- list:
- 1: primary mouse button (not available on stylus)
- 2: secondary mouse button, primary stylus button
- 3: middle mouse button, secondary stylus button
- 4: back button
- 5: forward button
- additional buttons can be represented by numbers
- greater than six:
- n: (n-2)th mouse button, ignoring any buttons that
- are explicitly back or forward buttons
- (n-4)th stylus button, again ignoring any
- explictly back or forward buttons
-
- down: true if the pointer is down (in pointer-down event or
- subsequent pointer-move events); false otherwise (in
- pointer-added, pointer-up, and pointer-removed events,
- and in pointer-move events that aren't between
- pointer-down and pointer-up events)
-
- primary: true if this is a primary pointer/touch (see above)
-
- obscured: true if the system was rendering another view on top of
- the sky application at the time of the event (this is
- intended to enable click-jacking protections)
+ pointer: an integer assigned to this touch or pointer when it
+ enters the system, never reused, increasing
+ monotonically every time a new value is assigned,
+ starting from 1 (if the system gets a new tap every
+ microsecond, this will cause a problem after 285
+ years)
+
+ kind: one of 'touch', 'mouse', 'stylus', 'inverted-stylus'
+
+ x: x-position relative to the top-left corner of the
+ surface of the node on which the event was fired
+
+ y: y-position relative to the top-left corner of the
+ surface of the node on which the event was fired
+
+ buttons: a bitfield of the buttons pressed, from the following
+ list:
+ 1: primary mouse button (not available on stylus)
+ 2: secondary mouse button, primary stylus button
+ 3: middle mouse button, secondary stylus button
+ 4: back button
+ 5: forward button
+ additional buttons can be represented by numbers
+ greater than six:
+ n: (n-2)th mouse button, ignoring any buttons that
+ are explicitly back or forward buttons
+ (n-4)th stylus button, again ignoring any
+ explictly back or forward buttons
+
+ down: true if the pointer is down (in pointer-down event or
+ subsequent pointer-move events); false otherwise (in
+ pointer-added, pointer-up, and pointer-removed events,
+ and in pointer-move events that aren't between
+ pointer-down and pointer-up events)
+
+ primary: true if this is a primary pointer/touch (see above)
+
+ obscured: true if the system was rendering another view on top
+ of the sky application at the time of the event (this
+ is intended to enable click-jacking protections)
When primary is true, the following fields are available:
- dx: if primary, then this is the delta from the x-position
- at the time that the pointer became primary.
+ dx: if primary, then this is the delta from the x-position
+ at the time that the pointer became primary.
- dy: if primary, then this is the delta from the x-position
- at the time that the pointer became primary.
+ dy: if primary, then this is the delta from the x-position
+ at the time that the pointer became primary.
When down is true:
- pressure: the pressure of the touch as a number ranging from 0.0,
- indicating a touch with no discernible pressure, to
- 1.0, indicating a touch with "normal" pressure, and
- possibly beyond, indicating a stronger touch; for
- devices that do not detect pressure (e.g. mice),
- returns 1.0
+ pressure: the pressure of the touch as a number ranging from
+ 0.0, indicating a touch with no discernible pressure,
+ to 1.0, indicating a touch with "normal" pressure, and
+ possibly beyond, indicating a stronger touch; for
+ devices that do not detect pressure (e.g. mice),
+ returns 1.0
- pressure-min: the minimum value that pressure can return for this
- pointer
+ pressure-min: the minimum value that pressure can return for this
+ pointer
- pressure-max: the maximum value that pressure can return for this
- pointer
+ pressure-max: the maximum value that pressure can return for this
+ pointer
When kind is 'touch', 'stylus', or 'stylus-inverted':
- distance: distance of detected object from surface (e.g. distance
- of stylus or finger from screen), if supported and down
- is not true, otherwise 0.0.
+ distance: distance of detected object from surface (e.g.
+ distance of stylus or finger from screen), if
+ supported and down is not true, otherwise 0.0.
- distance-min: the minimum value that distance can return for this
- pointer (always 0.0)
+ distance-min: the minimum value that distance can return for this
+ pointer (always 0.0)
- distance-max: the maximum value that distance can return for this
- pointer (0.0 if not supported)
+ distance-max: the maximum value that distance can return for this
+ pointer (0.0 if not supported)
When kind is 'touch', 'stylus', or 'stylus-inverted' and down is true:
- radius-major: the radius of the contact ellipse along the major axis,
- in pixels
+ radius-major: the radius of the contact ellipse along the major
+ axis, in pixels
- radius-minor: the radius of the contact ellipse along the major axis,
- in pixels
+ radius-minor: the radius of the contact ellipse along the major
+ axis, in pixels
- radius-min: the minimum value that could be reported for
- radius-major or radius-minor for this pointer
+ radius-min: the minimum value that could be reported for
+ radius-major or radius-minor for this pointer
- radius-max: the maximum value that could be reported for
- radius-major or radius-minor for this pointer
+ radius-max: the maximum value that could be reported for
+ radius-major or radius-minor for this pointer
When kind is 'touch' and down is true:
- orientation: the angle of the contact ellipse, in radians in the range
- -pi/2 < orientation <= pi/2
- ...giving the angle of the major axis of the ellipse with
- the y-axis (negative angles indicating an orientation
- along the top-left / bottom-right diagonal, positive
- angles indicating an orientation along the top-right /
- bottom-left diagonal, and zero indicating an orientation
- parallel with the y-axis)
+ orientation: the angle of the contact ellipse, in radians in the
+ range
+ -pi/2 < orientation <= pi/2
+ ...giving the angle of the major axis of the ellipse
+ with the y-axis (negative angles indicating an
+ orientation along the top-left / bottom-right
+ diagonal, positive angles indicating an orientation
+ along the top-right / bottom-left diagonal, and zero
+ indicating an orientation parallel with the y-axis)
When kind is 'stylus' or 'stylus-inverted':
- orientation: the angle of the stylus, in radians in the range
- -pi < orientation <= pi
- ...giving the angle of the axis of the stylus projected
- onto the screen, relative to the positive y-axis of the
- screen (thus 0 indicates the stylus, if projected onto
- the screen, would go from the contact point vertically
- up in the positive y-axis direction, pi would indicate
- that the stylus would go down in the negative y-axis
- direction; pi/4 would indicate that the stylus goes up
- and to the right, -pi/2 would indicate that the stylus
- goes to the left, etc)
-
- tilt: the angle of the stylus, in radians in the range
- 0 <= tilt <= pi/2
-
- ...giving the angle of the axis of the stylus, relative
- to the axis perpendicular to the screen (thus 0
- indicates the stylus is orthogonal to the plane of the
- screen, while pi/2 indicates that the stylus is flat on
- the screen)
+ orientation: the angle of the stylus, in radians in the range
+ -pi < orientation <= pi
+ ...giving the angle of the axis of the stylus
+ projected onto the screen, relative to the positive
+ y-axis of the screen (thus 0 indicates the stylus, if
+ projected onto the screen, would go from the contact
+ point vertically up in the positive y-axis direction,
+ pi would indicate that the stylus would go down in the
+ negative y-axis direction; pi/4 would indicate that
+ the stylus goes up and to the right, -pi/2 would
+ indicate that the stylus goes to the left, etc)
+
+ tilt: the angle of the stylus, in radians in the range
+ 0 <= tilt <= pi/2
+ ...giving the angle of the axis of the stylus,
+ relative to the axis perpendicular to the screen (thus
+ 0 indicates the stylus is orthogonal to the plane of
+ the screen, while pi/2 indicates that the stylus is
+ flat on the screen)
Wheel events
@@ -228,28 +229,28 @@ Wheel events
When a wheel input device is turned, a 'wheel' event that bubbles is
fired at the application's document, with the following fields:
- wheel: an integer assigned to this wheel by the system. The same
- wheel on the same system must always be given the same ID.
- The primary wheel (e.g. the vertical wheel on a mouse)
- must be given ID 1.
-
- delta: an floating point number representing the fraction of the
- wheel that was turned, with positive numbers representing
- a downward movement on vertical wheels, rightward movement
- on horizontal wheels, and a clockwise movement on wheels
- with a user-facing side.
-
-Additionally, if the wheel is associated with a pointer (e.g. a mouse
-wheel), the following fields must be present also:
-
- pointer: the integer assigned to the pointer in its 'pointer-add'
- event (see above).
-
- x: x-position relative to the top-left corner of the display,
- in global layout coordinates
-
- y: x-position relative to the top-left corner of the display,
- in global layout coordinates
+ wheel: an integer assigned to this wheel by the system. The
+ same wheel on the same system must always be given the
+ same ID. The primary wheel (e.g. the vertical wheel on
+ a mouse) must be given ID 1.
+
+ delta: an floating point number representing the fraction of
+ the wheel that was turned, with positive numbers
+ representing a downward movement on vertical wheels,
+ rightward movement on horizontal wheels, and a
+ clockwise movement on wheels with a user-facing side.
+
+ Additionally, if the wheel is associated with a pointer (e.g. a
+ mouse wheel), the following fields must be present also:
+
+ pointer: the integer assigned to the pointer in its
+ 'pointer-add' event (see above).
+
+ x: x-position relative to the top-left corner of the
+ display, in global layout coordinates
+
+ y: x-position relative to the top-left corner of the
+ display, in global layout coordinates
Note: The only wheels that are supported are mouse wheels and physical
dials. Track balls are not reported as mouse wheels.
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698