Open Bug 1317162 Opened 9 years ago Updated 3 years ago

Look into private browsing context for identity api

Categories

(WebExtensions :: General, defect, P3)

49 Branch
defect

Tracking

(Not tracked)

People

(Reporter: mixedpuppy, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: triaged)

We do an an XHR call and open a window in the identity api. We need to see if we need to do something for the calling context.
Chrome apparently disables it in incognito: https://stackoverflow.com/questions/32777079
The google specific APIs being discussed on the thread mentioned in comment #1 are not implemented in our identity api. There is no reason to disable the API we implement, but we do need to consider whether we need to do additional work to address the user context.
Assignee: nobody → mixedpuppy
Whiteboard: tr
Priority: -- → P1
Whiteboard: tr → triaged
This is an assigned P1 bug without activity in two weeks. If you intend to continue working on this bug for the current release/iteration/sprint, remove the 'stale-bug' keyword. Otherwise we'll reset the priority of the bug back to '--' on Monday, August 28th.
Keywords: stale-bug
Keywords: stale-bug
This should only be an issue if we implement the other identity apis (ie hooking into fxa in bug 1320862)
Assignee: mixedpuppy → nobody
Blocks: 1320862
Priority: P1 → P3
Product: Toolkit → WebExtensions
Component: Untriaged → General
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.