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

Mixed Content: express UI requirements imperatively #412

Open
annevk opened this issue Jul 3, 2015 · 3 comments
Open

Mixed Content: express UI requirements imperatively #412

annevk opened this issue Jul 3, 2015 · 3 comments
Labels

Comments

@annevk
Copy link
Member

annevk commented Jul 3, 2015

It would help if the allow/deny algorithms Fetch invokes also indicate what happens to the UI. See w3c/ServiceWorker#119 (comment) and previous comments for some of the confusion not having this caused. (Apart from the general difficulty of reading all these specifications.)

@mikewest
Copy link
Member

mikewest commented Jul 6, 2015

UI is generally something that we're not trying to specify, other than in fairly broad strokes. What is it specifically that you'd like to see hooked via Fetch (there are lots of questions in that thread...)?

@annevk
Copy link
Member Author

annevk commented Jul 6, 2015

That even though something is allowed to be fetched (or retrieved from the Cache API), mostly due historical incompetence of browsers and network effects, a Mixed Content SHOULD be displayed somewhere.

@mikewest mikewest added the MIX label Jul 9, 2015
@annevk
Copy link
Member Author

annevk commented Jul 14, 2015

You can now use "request's window" for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants