New issue
Advanced search Search tips

Issue 901539 link

Starred by 1 user

Issue metadata

Status: Closed
Owner: ----
Closed: Nov 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Suggestion chips not updating with recently opened apps

Project Member Reported by mkarkada@chromium.org, Nov 2

Issue description

Chrome OS Version: 11151.19.0, 71.0.3578.31 beta channel nocturne

What steps will reproduce the problem?
(1) Open launcher 
(2) Launch 2-3 apps like Files app, Playstore, Youtube app
(3) 

What is the expected result?
Suggestion chips must be updated with recently opened apps

What happens instead?
Suggestion chips (or the Recent apps list) is not updating. 

Issue not observed for the same build on caroline
 
Owner: ginko@chromium.org
Investigating this with my nocturne/caroline
Does not repro beyond what is described in 894898, and behaves identically between caroline and nocture in M72;

AKA: This doesn't repro in ToT

Going to investigate an M71 build on both devices, now
Doesn't repro on nocturne beyond  http://crbug.com/894898  in:

chrome: 71.0.3578.38
chromeos: 11151.6.0

It might be specifically just that one version.
switching to that specific chrome version (this last one was the branch head)
I still couldn't repro this beyond  http://crbug.com/894898  in:

chrome: 71.0.3578.31
chromeos: 11151.6.0

The only remaining thing to check is if it was a chromeOS version change that caused this
Owner: ----
Status: Unconfirmed (was: Untriaged)
I matched the version of the OS/Chrome exactly, but still can't repro this bug.

Here's a video of it working on this build on nocturne:
https://photos.app.goo.gl/joxpmbDnoPQ2X7p4A

Please let me know if there are additional steps to trigger this state.

We may want to close/remove release blocker
Status: Closed (was: Unconfirmed)
Please re-open with additional repro details if this is still an issue,
also see https://bugs.chromium.org/p/chromium/issues/detail?id=894898 and ensure this is a separate issue.

Sign in to add a comment