This repository has been archived by the owner on Aug 7, 2024. It is now read-only.
Remove line about NETWORK wildcards for Firefox #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
http://codebits.glennjones.net/appcache/network/index.html indicates that Firefox has no problem with "*" as a NETWORK entry, and furthermore that browsers *do* have problems when using "http://*" and "https://*" as entries (this is the behavior I have been seeing in Chrome, and http://manifest-validator.com/validate throws up errors on those lines).
stuartpb
added a commit
to stuartpb/hashblot
that referenced
this pull request
Feb 19, 2014
hazeledmands
pushed a commit
to hazeledmands/appcachefacts
that referenced
this pull request
Apr 15, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://codebits.glennjones.net/appcache/network/index.html indicates that Firefox has no problem with "" as a NETWORK entry, and furthermore that browsers do have problems when using "http://" and "https://*" as entries (this is the behavior I have been seeing in Chrome, and http://manifest-validator.com/validate throws up errors on those lines).