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

Issue 788856 link

Starred by 1 user
Status: Duplicate
Merged: issue 775532
Owner: ----
Closed: Nov 2017
Cc:
dmazz...@chromium.org
jinsuk...@chromium.org
█ vtsaran@chromium.org
candr...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocked on:
issue 775532


Sign in to add a comment

TalkBack gets stale DOM content of pages in embedded web views

Project Member Reported by ibobra@chromium.org, Nov 27 2017 
Chrome Version: latest Canary builds
OS: Android

What steps will reproduce the problem?
(1) Launch TalkBack, Settings > Accessibility > TalkBack.
(2) Install Chrome Canary and make it a default for browsing and web view. Also, make sure to enable "mobile-friendly" option in chrome://flags.
(3) Open Amazon App
(4) Touch and explore

What is the expected result?
TalkBack user should be able to explore and hear the contents of the  page at all times.

What happens instead?
The contents of the page can only be explored on the second time, not the first time. On the first time an empty view is presented to TalkBack instead.

Comment 1 by ibobra@chromium.org, Nov 27 2017

Cc: vtsaran@chromium.org dmazz...@chromium.org

Comment 2 by vtsaran@google.com, Nov 27 2017 

This behavior also occurs when the web view is spawned from another process. For example,
Scenario #1:
1. Amazon shows a notification on the status bar.
2. Pull down notification shade and activate the notification. Amazon app should open with a web view containing the content related to the notification.
3. Explore the screen and observe.

Scenario #2:
1. From Google's "your feed" (either in the Google app or from the home screen) pick an article, tap on it.
2. A page will open in embedded Chrome. If the content triggers "mobile friendly" flag,, tap on the button to instantiate the view.
3. Touch the content area and observe.

Comment 3 by ibobra@chromium.org, Nov 29 2017

Blockedon: 775532

Comment 4 by ibobra@chromium.org, Nov 29 2017

Labels: M-64 ReleaseBlock-Stable M-63

Comment 5 by cma...@chromium.org, Nov 30 2017 

ibobra@ is this a regression in M63?

Comment 6 by cma...@chromium.org, Nov 30 2017

Cc: candr...@chromium.org

Comment 7 by ibobra@chromium.org, Nov 30 2017 

I believe it is a regression.

The bug is very hard to reproduce and so we took help from the testing team. This is what we got from them:

Good Build :63.0.3224.4
Bad  Build  :63.0.3226.0,63.0.3231.0

Comment 8 by ibobra@chromium.org, Nov 30 2017

Cc: jinsuk...@chromium.org

Comment 9 by dmazz...@chromium.org, Nov 30 2017

Mergedinto: 775532
Status: Duplicate (was: Untriaged)
Only one merge is needed, so I'm just going to mark this as a duplicate of 775532 to eliminate confusion. There are different repros but one underlying bug and one merge needed.
►

Sign in to add a comment