Define basic address space inheritance rules. #37
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.
This PR starts converting English language requirements into actual patches to the HTML (mostly) and Fetch (a tiny bit) specs.
It patches Fetch minimally to support defining the HTML changes, mostly by defining an address space property on fetch responses. The changes to HTML are more extensive, but I am not yet sure they are enough. I think work remains to be done on
blob:
URLs, and I need to check what happens during navigations to coverdata:
andjavascript:
URLs. Any pointers there are appreciated.Along the way, I renamed
address space
toIP address space
, aligning with the URL spec's IPv{4,6} address concepts.This PR furthers #27 without fixing it entirely yet.