Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a browsing context with name "_private" #493

Closed
musically-ut opened this issue Jan 10, 2016 · 2 comments
Closed

Add a browsing context with name "_private" #493

musically-ut opened this issue Jan 10, 2016 · 2 comments
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest

Comments

@musically-ut
Copy link

Most browsers now have a private browsing mode, which offer similar features, i.e. browsing history is not recorded, cookies are not saved, localstorage is flushed when the context ends, and some other forms of isolation.

I think it would make sense to formalize such a browsing context and allow a webpage to specify that the target for an a link is _private, so that the page opens in private mode.

Does this make sense or are there better alternatives/previous proposals which deal with this?

Also, I am not sure which is the best venue/spec to approach for this; the HTML spec seems to be the most appropriate. If I am wrong, kindly guide me to the correct venue.

@annevk annevk added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest labels Jan 11, 2016
@annevk
Copy link
Member

annevk commented Jan 11, 2016

Could you run this proposal through the https://lists.w3.org/Archives/Public/public-webappsec/ mailing list perhaps? Similar things have been proposed, but nothing quite like this.

@annevk
Copy link
Member

annevk commented Jul 6, 2016

So while I think there's probably something here, I don't think we have the architecture sorted quite yet to enable this and the use cases to support it. Going to close this for now. Further work on isolation within the WebAppSec community might enable this one day.

@annevk annevk closed this as completed Jul 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest
Development

No branches or pull requests

2 participants