246157 - Doesn't correctly display the &ntilde character as that n with a tilde over it in the word pinata (e.g. shows pi&ntlideata).

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[gheller]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040514
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040514

In IE, heck in Netscape 3, the special character &ntlide is displayed as an n
with a tilde over it.  But Mozilla doesn't appear to do this correctly. 
Example, on the following page:

http://www.geocities.com/ghohenzollern/burn03/Index.htm

and search for "pi&ntildeata"  and you'll find it.  When you shouldn't because
it should display that special character instead of &ntilde.

Reproducible: Always
Steps to Reproduce:
1.view the website http://www.geocities.com/ghohenzollern/burn03/Index.htm
2.Use "Find in this Page" from the Edit menu
3.Search for "pi&ntildeata"

Actual Results:  
It found that word, complete with the ampersand and all.

Expected Results:  
It should not have found that word, because it should have been displayed with
the special character (n with a tilde above it) instead of as &ntlide.

I am unaware of any special themes or anything I'm using, so I'm probably not
using them.

Comment 1

[Bill Mason]

A semicolon is supposed to be after the &ntilde

That's why.

Comment 2

[gheller]

(In reply to comment #1)
> A semicolon is supposed to be after the &ntilde
> 
> That's why.

<Slap on head>  Ah yes.  My screen resolution must be too great for my eyes
anymore.  There it is, that pesky semicolon on every page I looked at trying to
find the right code for that N.  I'm getting old already, and I'm only 28.  

I shall put one there, and yet, it seems odd that the character displays under
IE and Netscape 3 without the semicolon.  I wonder if anyone's told Microsoft
they're doing it wrong.  Not that they'd listen, after all, if their browser
shows the character even when people forget the semicolon, then that just makes
Mozilla look bad when viewing those pages.  You might consider doing it their
way anyway, even though it's technically wrong.  Netscape 3 apparently did. 
Haven't tried 4 though.  :)

-Gabe