Fold touchEvents from extensions.html into index.html

[bradleyneedham]

Partially Closes #165

The following tasks have been completed:

• Modified Web platform tests (link to pull request)

Implementation commitment:

• WebKit (https://bugs.webkit.org/show_bug.cgi?id=)
• Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=1143942#c14)
• Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)

Standards positions:

• Webkit (Gamepad multitouch API WebKit/standards-positions#110)
• Gecko (Gamepad multitouch API mozilla/standards-positions#724)

Resources:

• Explainer (https://github.com/bradleyneedham/gamepad/blob/multitouch-explainer/multitouch_explainer.md)
• Gamepad Tests (https://github.com/bradleyneedham/gamepadtest)
• Tag Review (Gamepad Extensions API touch input w3ctag/design-reviews#799)

---

Preview | Diff

[bradleyneedham]

I believe the failure of the tidy action is an indentation error on line 19 of .github/workflows/tidy.yml. The with needs to be even with the start of uses.
Current is:

line 18:             - uses:
line 19:             with:

Should be:

line 18:             - uses:
line 19:               with:

[bradleyneedham]

I am moving this from "Draft". Any help with spotting the reason for the validate failure is appreciated.

Also I think that newline: LF should be added to the tidyconfig.txt to prevent local runs of tidy on windows from adding all CRLF.

[marcoscaceres]

@bradleyneedham, sorry, I just need to double check if this is in scope of the Working Group. I seem to recall there was some concerns from some members around anything "touch" related, so just need to make sure it's all fine.

Shouldn't be too long!

[marcoscaceres]

This should really be part of a Model section... or wherever the general idea of gamepad is defined.

[marcoscaceres]

Suggested change

	<dfn>touch surface</dfn> is a surface that can detect contact from a
	<dfn data-dfn-for="gamepad">touch surface</dfn> is a surface that can detect contact from a

[marcoscaceres]

Suggested change

	<dfn>touch surface enumeration order</dfn> is an ordered listing of all
	<dfn data-dfn-for="gamepad">touch surface enumeration order</dfn> is an ordered listing of all

[marcoscaceres]

Is there a concept we can maybe use from Pointer Events instead?

[marcoscaceres]

Ok, so... are these really touch "events"? If we look at GamepadTouch, it's not an "Event" at all, so this is a misnomer.

They are more like snapshots of touch points.

[marcoscaceres]

As above... I think it's incorrect to call these "touch events". They are activation points on the track pad at some specific moment in time.

[marcoscaceres]

This seems to assume the gamepad is a live object? I don't think this correct. Each gamepad object is just a snapshot in time.

[marcoscaceres]

Suggested change

	readonly attribute Float32Array position;
	readonly attribute Uint32Array? surfaceDimensions;
	Float32Array position;
	Uint32Array surfaceDimensions;

[marcoscaceres]

Suggested change

	readonly attribute FrozenArray<GamepadTouch>? touchEvents;
	readonly attribute FrozenArray<GamepadTouch>? touches;

[bradleyneedham]

Just getting to back to this and wanted to verify our discussion at the last meeting.
In general is the following the suggested approach?

        dictionary GamepadTouch {
          unsigned long touchId;
          Float32Array position;
        };

        dictionary GamepadSurface {
          octet surfaceId;
          FrozenArray<GamepadTouch>? touches;
          Uint32Array surfaceDimensions;
        };

        interface Gamepad {
...
          readonly attribute FrozenArray<GamepadSurface>? surfaces;
...
        };

[nondebug]

If I remember correctly, we decided on maplike interfaces for the surfaceId -> GamepadSurface and touchId -> sequence<GamepadTouch> maps. I think it should look something like this:

        dictionary GamepadTouch {
          Float32Array position;
        };

        interface GamepadTouchMap {
          readonly maplike<unsigned long, sequence<GamepadTouch>>;
        };

        dictionary GamepadSurface {
          GamepadTouchMap touches;
          Uint32Array surfaceDimensions;
        };

        interface GamepadSurfaceMap {
          readonly maplike<octet, GamepadSurface>;
        };

        interface Gamepad {
...
          readonly attribute GamepadSurfaceMap surfaces;
...
        };

[marcoscaceres]

Suggested change

	List of generated touch events.
	A [=list=] of touch that are represented as {{GamepadTouch}}s. The ordering is hardware or platform specific.

[marcoscaceres]

Note: this is an optimization... as you say, this can't be assured.

[marcoscaceres]

Suggested change

	A list of {{GamepadTouch}} events generated from all touch
	A [=list=] of {{GamepadTouch}} generated from all touch

[marcoscaceres]

Let's make it empty.

[marcoscaceres]

Suggested change

	<li>Remove any existing events from
	{{Gamepad}}.{{Gamepad/[[touches]]}}.
	<li>[=List/empty=] {{Gamepad}}.{{Gamepad/[[touches]]}}.

[marcoscaceres]

Use DOMRect/point terminology.

[marcoscaceres]

Note, move away from calling it "*Event". Call it |gameTouch|, and

Suggested change

	<li>Set |touchEvent|.{{GamepadTouch/surfaceDimensions}}[0] to
	<li>Let |gamepadTouch| be a newly created {{GamepadTouch}.</li>
	<li>Set |gamepadTouch|.{{GamepadTouch/surfaceDimensions}}[0] to

[marcoscaceres]

oops, increment twice

[gabrielsanbrito]

Instead of using 0 here, should we store a touchId counter in an internal slot somewhere? Maybe in the target Gamepad object?

[marcoscaceres]

Suggested change

	<li>Return whatever is in the internal slot.
	<li>Return the [=list=] of the {{Gamepad/[[touches]]} internal slot.

[marcoscaceres]

Suggested change

	An empty [=list=]
	Initialize to an [=list/empty=] [=list=]

[marcoscaceres]

Suggested change

	List of generated touches.
	Holds the list of user-generated touches, if any. If the gamepad does not support touch surfaces, then the list will remain empty.

[marcoscaceres]

Suggested change

	surfaces. If the device does not support touches, then an empty
	[=list=].
	surfaces.

[marcoscaceres]

Suggested change

	<li>Run the steps to [=refresh touches=] for |gamepad|.
	<li>Run the steps to [=record touches=] for |gamepad|.

[marcoscaceres]

Suggested change

	To <dfn>refresh touches</dfn> for |gamepad:Gamepad|, run the
	To <dfn>record touches</dfn> for |gamepad:Gamepad|, run the

[marcoscaceres]

Suggested change

	<li>Remove any existing objects from
	{{Gamepad}}.{{Gamepad/[[touches]]}}.
	</li>
	<li>Assert: {{Gamepad}}.{{Gamepad/[[touches]]}} is [=list/empty=].
	</li>

[marcoscaceres]

Suggested change

	<li>Let |touch:GamepadTouch| be a {{GamepadTouch}}.
	<li>Let |touch:GamepadTouch| be a newly created {{GamepadTouch}} object.