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

Issue 729985 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Land QO 120.2070.2076 on CrOS trunk

Project Member Reported by hlo@chromium.org, Jun 6 2017

Issue description

This a tracking bug to update "Quickoffice Chrome" on CrOS ToT (trunk) to QO version
120.2070.2076
 

Comment 1 by hlo@chromium.org, Jun 6 2017

Cc: michae...@chromium.org
+michaelpg 
Hi Michael, wanted to make you aware of this as it may be that this also needs merging into M60 also. I can merge this into ChromeOS trunk but do not know how to merge this into M60 release - hoping you can pick this up or know someone who can. 

Some background for you, after the release made last week for the QO looping issue, the QO Chrome team continued their testing. They found that there was a regression seen where: 
[Chromebook Specific] Focus should move to browser while opening document in Chrome QO from file manager. This new release fixes that issue. 

Details of the regression issue below: 
Steps to reproduce-
1.On Chromebook, go to file manager
2.Double tap on Microsoft Office document to open in Chrome QO
3.Observe the behaviour of file manager
Expected-
Focus should move to browser while opening document in Chrome QO from file manager
Actual-
Focus remains on file manager thus document opened in new tab of Chrome browser is not visible to user.
Scenario # 2-
Keep Chrome browser minimized and open a document from file manager. >> This also results in the same problem. Document is opened in browser but user can't view unless he/she maximize Chrome browser.
Scenario # 3-
Select a document in file manager >> Right click and select option - Open with Chrome QO Document is opened in browser but user can't view unless he/she minimize the file manager.
Options



I'll land this now.
Status: Fixed (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 7 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/src-internal.git/+/98ade0a67cd62025e16d70226643163d2cc7a396

commit 98ade0a67cd62025e16d70226643163d2cc7a396
Author: Michael Giuffrida <michaelpg@google.com>
Date: Wed Jun 07 00:32:57 2017

Comment 5 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment