New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 903461 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 897906
Owner: ----
Closed: Nov 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Unable to move objects in SeeSaw webapp

Project Member Reported by bigo@chromium.org, Nov 8

Issue description

Chrome version: 70.0.3538.76
OS version: Chrome OS
Case#: 17451507

Description: Using the SeeSaw learning app (https://chrome.google.com/webstore/detail/seesaw-the-learning-journ/adnohgfkodfphemhddnmikhflkolfjfh)

In certain games (Letter Match for example), you are required to move object around on the screen.  This no longer works for touch input.


Steps to reproduce: 

1) Open SeeSaw: The learning Journal app (This loads the website in the browser)
2) Sign in as a teacher or student
3) Add an activity that requires moving object on the screen (Letter Match, Shape Sort)


Current Behavior / Reproduction: 
A text box comes up instead, which you are unable to move, cannot move any objects.

Expected Behavior: 
Able to move objects to interact with the game

Feedback logs from a device on 70: https://listnr.corp.google.com/product/208/report/85772796650



 
Components: Blink>Input
Also adding feedback link from the same device on version 69 where this was working correctly:

https://listnr.corp.google.com/product/208/report/85772767989?dateRange=All
Cc: nzolghadr@chromium.org
nzolghadr, would you be able to help triage this issue?
Cc: eirage@chromium.org
Do you know when this stopped working?

It is probably related to deprecating the old touch apis we had on document. CC'ing Ella for that. Do you have any contact with the developers of the app?
Status: WontFix (was: Untriaged)
Oh. Just noticed that it was working on 69. So it should be very much related to 
https://www.chromestatus.com/feature/4764225348042752

That change was intended and we expect developers to use new APIs like adding touch listeners with AddEventListener and check the window.maxTouchPoints to check the capability of touch screen if they are looking for that. Although I prefer it they switch to pointerevents altogether.
Understood.  Thanks for the help!
Mergedinto: 897906
Status: Duplicate (was: WontFix)

Sign in to add a comment