New issue
Advanced search Search tips

Issue 884080 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

QuickView / MetadataboxController JS error when selected a Directory in a FSP

Project Member Reported by lucmult@chromium.org, Sep 14

Issue description

When we visualize a folder in Drive QuickView errors in JS console with:
"Unchecked runtime.lastError: Only local directories are supported."

With stack trace:

main_scripts.js:12439 undefined
(anonymous) @ main_scripts.js:12439
Promise.catch (async)
QuickViewController.updateQuickView_ @ main_scripts.js:38231
QuickViewController.display_ @ main_scripts.js:38164
QuickViewController.onFileSelectionChanged_ @ main_scripts.js:38184
dispatchEvent @ main_scripts.js:2975
dispatchSimpleEvent @ main_scripts.js:1617
FileSelectionHandler.onFileSelectionChanged @ main_scripts.js:28878
dispatchEvent @ main_scripts.js:2975
endChange @ main_scripts.js:5115
set selectedIndexes @ main_scripts.js:4945
set selectedIndex @ main_scripts.js:4960
QuickViewController.onQuickViewKeyDown_ @ main_scripts.js:38150



 
Components: Platform>Apps>FileManager
The error takes a few seconds to show up after opening QuickView
Owner: lucmult@chromium.org
Status: Assigned (was: Untriaged)
Summary: QuickView / MetadataboxController JS error when selected a Directory in a FSP (was: QuickView / MetadataboxController JS error when selected a Directory in Drive)
This is fixed for DriveFS by https://chromium-review.googlesource.com/c/chromium/src/+/1385687.

It can still come up for FSP filesystems though. We can avoid it by checking chrome.runtime.lastError in the selection changed case or by skipping the chrome.fileManagerPrivate.getDirectorySize() call entirely for unsupported filesystem types.

Sign in to add a comment