Skip to content

Commit 6557d81

Browse files
committed
New release
1 parent be23902 commit 6557d81

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Here follows an example table that shows a few cases of ambiguous and non-ambigu
6262

6363
* The function `JSEntities.parseTree()` replaces the text of *all* the attributes contained in a DOM tree. Since some of these attributes might have been assigned via JavaScript and might no longer contain strings (as, for example, `mySpanElement.onlick = clickMe;` – where `typeof mySpanElement.onlick` is usually a `"function"` and not a `"string"`), it is preferable to launch `JSEntities.parseTree()` *before any other script*.
6464
* The string segments enclosed within `&{` and `};` are passed **verbatim** to [`eval()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval) and executed in the global scope.
65-
* Right curly brackets followed by a semicolon (`};`) *do not* end the Javascript entity until they no longer constitute syntactically valid JavaScript code &ndash; as the segment `'red' };` in `<p style="color: &{var myObject = { 'color': 'red' }; myObject.color;};">Hi!</p>`
65+
* A right curly bracket followed by a semicolon (`};`) *does not* end the Javascript entity until it no longer expresses a syntactically valid JavaScript symbol &ndash; as the segment `'red' };` in `<p style="color: &{var myObject = { 'color': 'red' }; myObject.color;};">Hi!</p>`
6666
* Within JavaScript entities, the three characters `<`, `>` and `"` must *always* be encoded (respectively, `&lt;`, `&gt;` and `&quot;`). As for the character `&`, it must be encoded (`&amp;`) when it represents an ambiguous ampersand &ndash; as in, for example, `var bContinue=bAccept&&bAvailable;` (see above).
6767

6868
Enjoy the entities!

0 commit comments

Comments
 (0)