Each task item in the menu is represented as a structure (title, verb, icon, ...) at the level of fileManagerPrivate API.

https://codereview.chromium.org/1872223002/diff/300001/chrome/common/extensions/api/file_manager_private.idl

and combined into a menu item string at the UI side

https://codereview.chromium.org/1872223002/diff/300001/ui/file_manager/file_manager/foreground/js/file_tasks.js

I believe splitting them to two menues shouldn't be so hard.

weifangsun@,
We already have a share button for Drive files.
Should we merge it to the share menu?

Thank you kinaba@!
We seems to have enough information to separate share actions.

weifangsun@, is it OK if share actions can not be default actions? (Default action is an action executed on double-click on a file).
I guess most share actions are generic tasks, so they can not be default actions anyway. But I haven't confirmed it yet.

All share actions from ARC are already generic and cannot be default anyway:
https://cs.chromium.org/chromium/src/chrome/browser/chromeos/file_manager/arc_file_tasks.cc?type=cs&l=150


I don't know any other users of this verb outside ARC... I think it is negligible.

fukino@, thanks for the initial investigation!

FYI, we've put together a one-pager and mocks at go/fileapp-osi | go filesapp-osi-mocks.

- For the share button, please see mocks - We'd like to update this button and move the current Drive share button as a specific Drive action.
- To confirm, share actions do not need to be available to set as a default action. (only Open With)

Thank you for the docs!
The correct links seems to be go/filesapp-osi and go/filesapp-osi-mocks :)

I added some comments on go/filesapp-osi-mocks .

Let me merge this issue to a tracking bug ( issue 740816 ) for go/filesapp-osi.
(since the request is not only about the menu UI change).