|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IE4/5 HTML parsing bug
- To: NTBUGTRAQ
LISTSERV.NTBUGTRAQ.COM - Subject: Re: IE4/5 HTML parsing bug
- From: Nick Jones <nick
ADVALUE.COM> - Date: Tue, 27 Apr 1999 15:07:49 -0400
- Approved-By: Russ.Cooper
RC.ON.CA - Importance: Normal
- In-Reply-To: <339041D6C26CD11187C500805FF518FC0160634F
delta.tjg> - Reply-To: Nick Jones <nick
ADVALUE.COM> - Sender: Windows NT BugTraq Mailing List <NTBUGTRAQ
LISTSERV.NTBUGTRAQ.COM>
This isn't limited to IE. Netscape Navigator 4.5 has the same issue, which seems to be the result of complacent parsing of HTML entities. All of these *should* start with "&" and end with ";" -- but the browsers are ignoring the requirement for the trailing semicolon. You'll find that any of the special characters supported by these browsers (like & and , to name some common ones) will have the same problem. - Nick
- References:
- IE4/5 HTML parsing bug
- From: Brooks Martin <MBrooks
TJGUK.COM>
- From: Brooks Martin <MBrooks
- IE4/5 HTML parsing bug
- Prev by Date: Re: bug in SP4 Acl Editor
- Next by Date: Re: IE4/5 HTML parsing bug
- Prev by thread: IE4/5 HTML parsing bug
- Next by thread: Re: IE4/5 HTML parsing bug
- Index(es):