Wrong Textparsing with &reg (not ®)

[[email protected]…]

If you try to write xxx&reg_xxx in a html context it will be shown as ® (...e®_b...)

Sample: $('#report').html("<div>rpt=sls_fleet_stat_tree&omit_olddata=true&ids=false&reg_by_month=false&cco_by_month=false</div>")

[Frank Glück <[email protected]…>]

or try this: $('#report').html("&regby")

[Frank Glück <[email protected]…>]

but it is a little bit difficult:

$('#report').html('&reg &amp &euro &lt &gt &hearts &copy &trade &pound')

[gibson042]

This is not under the control of jQuery, and not even a bug. See ​http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#consume-a-character-reference for the relevant HTML5 character reference parsing logic:

Consume the maximum number of characters [immediately after the U+0026 AMPERSAND] possible, with the consumed characters matching one of the identifiers in the first column of the ​named character references table (in a ​case-sensitive manner).

Note that reg appears in the ​table, so the first 4 characters of &regby should be consumed and replaced by U+00AE REGISTERED SIGN (®).

[Frank Glück <[email protected]…>]

If the character reference is being consumed as part of an attribute, and the last character matched is not a U+003B SEMICOLON character (;), and the next character is either a U+003D EQUALS SIGN character (=) or an alphanumeric ASCII character, then, for historical reasons, all the characters that were matched after the U+0026 AMPERSAND character (&) must be unconsumed, and nothing is returned.

So try: $('#report').html('&reg=&reg;&regby')

[dmethvin]

The point is, this is not a jQuery bug. If you have issues with the standard, contact the W3C and ask them to change the rules.