New issue
Advanced search Search tips

Issue 762626 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 3
Type: Bug-Regression



Sign in to add a comment

After an autest, MS office documents are not restoring their previous state.

Project Member Reported by mkarkada@chromium.org, Sep 6 2017

Issue description

Chrome OS Version: M61 (61.0.3163.80 beta build)
Chrome OS Platform: 9765.53.0 beta channel caroline, eve, daisy, minnie devices

Steps To Reproduce:
(1) Be on previous live public build. Open few MS office docs from Downloads folder- like .docx, .ppt, .xlsx.
(2) These docs are usually opened through Chrome office viewer (quick office component).
(3) Do auto update (autest).
(4) These documents are not reloaded automatically. 
(5) Reopen these documents. Perform sign out and sign in.
(6) Again observed that these documents are not reloaded automatically.

Expected Result:
After an autest, MS office documents should regain their previous state. Hence, office documents must be in open state as before.

Actual behavior:
Instead, a message is displayed saying 'Unable to determine the file to open'.
 
Cc: weifangsun@chromium.org

Comment 2 Deleted

Comment 3 Deleted

Labels: Restrict-View-Google
Components: -Platform>Apps>Default>Quickoffice -Platform>Apps>Default>ChromeOffice Platform>Apps>FileManager
Labels: -M-61
mkarkada@ - Is this still an issue?
Labels: -Restrict-View-Google
@weifangsun, Yes, this problem still happens on latest M69 ToT as well as latest M68 beta. Local MS docs (from Drive or Downloads folder) don't reload automatically after an AU or re-sign in. 

I'm not very sure if this is an issue or intended behavior. 

Note that I don't see this issue with online MS docs opened directly from the web. They do reload after an AU or re-sign in.
Cc: slangley@chromium.org
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
mkarkada@ - Thanks for checking! In that case, I'll keep issue open as a known issue in our backlog. It sounds like it could be related to the QuickOffice extension for opening MS docs.

Sign in to add a comment