Re: [w3c/manifest] Shortcut item should have an "id" field (Issue #1020)

@mgiuca I apologize for being late to the game here.

I’m definitely in favor of allowing for an explicit `id` (or similar) field. In `translations` we’d talked about using order as the mechanism for providing the overrides, but I feel like that could become problematic over time. Also, having an author-provided id would unblock the dynamic shortcuts work, which is currently in a holding pattern, as it would enable a dev to target a specific manifest-defined shortcut and tweak it dynamically (for instance, appending the current song name to a "now playing" shortcut).

When the `id` is not specified, I think the URL-driven tuple probably makes sense, but I’m guessing we’ll hit the occasional snag if folks include (and change) query string params or if their URL structure changes over time. We should probably call that out in the spec as a note at least and push people to update their manifest with explicit shortcut IDs prior to migrating shortcut paths.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1020#issuecomment-988118653