sky/engine/core/frame/Settings.in - Issue 868133003: Remove touch events from Sky

Side by Side Diff: sky/engine/core/frame/Settings.in

Issue 868133003: Remove touch events from Sky (Closed) Base URL: git@github.com:domokit/mojo.git@master

Patch Set: Created 5 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

« no previous file with comments | « sky/engine/core/frame/NewEventHandler.cpp ('k') | sky/engine/core/page/EventHandler.h » ('j') | no next file with comments »

OLD	NEW
1 # Defines properties which are available on the Settings object.	1 # Defines properties which are available on the Settings object.

2 #	2 #

3 # Please think carefully before adding a new Setting. Some questions to	3 # Please think carefully before adding a new Setting. Some questions to

4 # consider are:	4 # consider are:

5 # - Should this be a RuntimeEnabledFeature instead? Settings are for things	5 # - Should this be a RuntimeEnabledFeature instead? Settings are for things

6 # which we support either values of at runtime. Features are set at renderer	6 # which we support either values of at runtime. Features are set at renderer

7 # process startup and are never changed. Features also tend to be set to a	7 # process startup and are never changed. Features also tend to be set to a

8 # value based on the platform or the stability of the code in question, where	8 # value based on the platform or the stability of the code in question, where

9 # as settings both codepaths need to be stable.	9 # as settings both codepaths need to be stable.

10 # - How will you ensure test coverage of all relevant values of your setting?	10 # - How will you ensure test coverage of all relevant values of your setting?

(...skipping 58 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
69	69

70 # Limited use by features which behave differently depending on the input	70 # Limited use by features which behave differently depending on the input

71 # devices available. For example, the pointer and hover media queries.	71 # devices available. For example, the pointer and hover media queries.

72 # Note that we need to be careful when basing behavior or UI on this -	72 # Note that we need to be careful when basing behavior or UI on this -

73 # just because a device is present doesn't mean the user cares about it	73 # just because a device is present doesn't mean the user cares about it

74 # or uses it (i.e. Chromebook Pixel users generally don't want to give up	74 # or uses it (i.e. Chromebook Pixel users generally don't want to give up

75 # screen real estate just because they happen to have a touchscreen).	75 # screen real estate just because they happen to have a touchscreen).

76 deviceSupportsTouch initial=false	76 deviceSupportsTouch initial=false

77 deviceSupportsMouse initial=true	77 deviceSupportsMouse initial=true

78	78

79 # This value indicates the number of simultaneous multi-touch points supported

80 # by the currently connected screen/digitizer that supports the most points.

81 # From Pointer Events spec:

82 # http://www.w3.org/TR/pointerevents/#widl-Navigator-maxTouchPoints

83 maxTouchPoints type=int, initial=0

84

85 DOMPasteAllowed initial=false	79 DOMPasteAllowed initial=false

86	80

87 unifiedTextCheckerEnabled initial=defaultUnifiedTextCheckerEnabled	81 unifiedTextCheckerEnabled initial=defaultUnifiedTextCheckerEnabled

88	82

89 # Some apps could have a default video poster if it is not set.	83 # Some apps could have a default video poster if it is not set.

90 defaultVideoPosterURL type=String	84 defaultVideoPosterURL type=String

91	85

92 smartInsertDeleteEnabled initial=defaultSmartInsertDeleteEnabled	86 smartInsertDeleteEnabled initial=defaultSmartInsertDeleteEnabled

93	87

94 selectionIncludesAltImageText initial=false	88 selectionIncludesAltImageText initial=false

(...skipping 27 matching lines...) Expand all Loading...
122	116

123 # These values are bit fields for the properties of available pointing devices	117 # These values are bit fields for the properties of available pointing devices

124 # and may take on multiple values (e.g. laptop with touchpad and touchscreen	118 # and may take on multiple values (e.g. laptop with touchpad and touchscreen

125 # has pointerType coarse and fine).	119 # has pointerType coarse and fine).

126 availablePointerTypes type=int, initial=PointerTypeNone, invalidate=MediaQuery	120 availablePointerTypes type=int, initial=PointerTypeNone, invalidate=MediaQuery

127 availableHoverTypes type=int, initial=HoverTypeNone, invalidate=MediaQuery	121 availableHoverTypes type=int, initial=HoverTypeNone, invalidate=MediaQuery

128	122

129 # These values specify properties of the user's primary pointing device only.	123 # These values specify properties of the user's primary pointing device only.

130 primaryPointerType type=PointerType, initial=PointerTypeNone, invalidate=MediaQu ery	124 primaryPointerType type=PointerType, initial=PointerTypeNone, invalidate=MediaQu ery

131 primaryHoverType type=HoverType, initial=HoverTypeNone, invalidate=MediaQuery	125 primaryHoverType type=HoverType, initial=HoverTypeNone, invalidate=MediaQuery

OLD	NEW