Correct HTML namespaces #489
Merged
Conversation
This file contains hidden or 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
Malvoz
commented
Jul 20, 2021
|
During processing of #515 I discovered that by correcting the namespace on GeoGratis resources e.g. this one, I can no longer 'force' the browser to parse the response with the XML parser, it sniffs the namespace and parses with the (X)HTML(?) parser, with the result being that it displays a very simple web page with only the text content rendered (the map-title). Not a big deal, better to have the correct namespace, but interesting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(See Maps4HTML/MapML-Specification#198)
@prushforth This PR only corrects current namespace declarations, but there are quite a few .mapml files that have
<mapml>elements without a namespace declaration. Should I fix that before we proceed to merge this PR?