Fixed basic XHTML problems. #801
Merged
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
|
Looks good. |
|
@lars-sh nice catch with VML! |
|
I see, thanks! |
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.
On strict XHTML sites that are even responding with the http content-type header for valid xhtml files Leaflet was broken in 0.3.1 and also in 0.4.
In order to fix basic usage (tested: OSM, Marker, Popup and Polyline) the VML detection need to be made "secure" and all of those html entities need to be replaced.
I guess this request could be interesting for a lot more people.
PS: For simplier testing, just rename your html files to xhtml files and test them.