[Normative] Capture the HTML entity behaviors#1
Closed
Huxpro wants to merge 1 commit into
Closed
Conversation
Let's be faithful to the de-facto and capture the HTML semantics to the spec. I haven't seen any practices specifying transipilers via ECMA-262 so this was a bit challenging may seems foreign. I ended up extending `Static Semantics: SV` to make it concise and (hopefully) accurate enough. I think this is a cool hack ;) - Introduced `JSXStringCharacter` and `JSXString` - Fix react#133 by using `::` to make problematic grammars lexcial I intentionally making the set of supported HTML entities implementation-defined to allow either HTML4 or HTML5 set but this is open to discuss.
Huxpro
force-pushed
the
html-char-ref
branch
from
016dcd9 to
ea9361f
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Let's be faithful to the de-facto and capture the HTML semantics
to the spec. I haven't seen any practices specifying transipilers
via ECMA-262 so this was a bit challenging may seems foreign.
I ended up extending
Static Semantics: SVto make it concise and(hopefully) accurate enough. I think this is a cool hack ;)
JSXStringCharacterandJSXString::to make problematic grammars lexcialI intentionally making the set of supported HTML entities
implementation-defined to allow either HTML4 or HTML5 set but
this is open to discuss.
Close react#126
Close react#4