Open Bug 662926 Opened 10 years ago Updated 7 years ago

When an app tab navigates to a different origin it should lose its app tab status

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

People

(Reporter: bsterne, Unassigned)

References

()

Details

I'm filing this bug as a follow-up to the Toolbarless app tab security review completed today.

When a user pins a tab as an app tab, we should guarantee that the tab always remains in the same origin (scheme, host and port) in order to keep the pinned status.  If the tab navigates to a different origin for any reason, whether user-initiated or not, the app tab should revert to a normal tab.
Actually, I believe the intended function is that they open in new tabs, which I think is a good idea. We don't want the app tab becoming unpinned unless the user explicitly chooses that option.
(In reply to comment #1)
> Actually, I believe the intended function is that they open in new tabs,
> which I think is a good idea.

Yes, this sounds like bug 598587.
This bug needs to address the case where the *page navigates itself*.  An app tab can currently set its window.location via script which can easily lead to a user thinking they're on a different page.
You need to log in before you can comment on or make changes to this bug.