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

Issue 897302 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

Run on startup

Project Member Reported by dxie@google.com, Oct 19

Issue description


 
Labels: Proj-Fugu
Labels: Type-Feature
Labels: Pri-1
Status: Available (was: Untriaged)
Cc: juberti@chromium.org
Owner: jsb...@chromium.org
Status: Assigned (was: Available)
gather requirement for this API.
Cc: benwells@chromium.org
Components: UI>Browser>WebAppInstalls Platform>Apps>Foundation
My assumption is that this is "launch the Desktop PWA when the system starts up" (or more accurately, a user logs in), but want confirmation. i.e. the equivalent to:

* Windows: adding a shortcut to the Startup folder
* MacOS: adding an item to Users & Groups > Login Items
* Linux/Unity: add item to Settings / Startup Applications

Or are there different use cases? Is there a difference between this and simply adding the PWA's icon to the OS-specific startup mechanism?
That mostly sounds right to me; we'd probably also want to pass flags to indicate whether the app should run as if clicked, or just in the background, with only its service worker running.
The other main use case is to ensure that Chrome is running at Startup so notifications etc. can work. This doesn't require the apps to be running in the foreground.

Comment 9 by dxie@chromium.org, Jan 17 (6 days ago)

Owner: dominickn@chromium.org
can you start a doc and gather the required usecases there? Once we get these, we can fan out the work.

Sign in to add a comment