Why is “®” being rendered as “®” without the bounding semicolon

Question

I\'ve been running into a problem that was revealed through our Google adwords-driven marketing campaign. One of the standard parameters used is \"region\". When a user se

Answer 1

1: The following markup is invalid in the first place (use the W3C Markup Validation Service to verify):

In the above example, the & character should be encoded as &, like so:

2: Browsers are tolerant; they try to make sense out of broken HTML. In your case, all possibly valid HTML entities are converted to HTML entities.