- From: Charles Reitzel <creitzel@rcn.com>
- Date: Mon, 02 Dec 2002 12:30:50 -0500
- To: "Hofmann Juergen (SaW/QSG1) *" <Juergen.Hofmann2@de.bosch.com>
- Cc: "'html-tidy@w3.org'" <html-tidy@w3.org>
Not sure that is wrong from a W3C compliance POV. From a functionality
POV, the predictable case is that IE6 will urlDecode the URL and NS6 will
not. We're still dumbing down for NS, I see.
Anyway, it shouldn't be too difficult to avoid escaping the URL for the
javascript: scheme. Can you log a bug at
http://sourceforge.net/tracker/?atid=390963&group_id=27659&func=browse?
take it easy,
Charlie
At 02:24 PM 11/29/2002 +0100, Hofmann Juergen (SaW/QSG1) * wrote:
>Tidy-Bug:
>HTML Tidy for Windows (vers 1st July 2002; built on Jul 18 2002, at
>14:24:17)
>
>1a. HTML-Code:
>74:...
>75: <P>
>76: Text <A HREF="javascript:parent.WindowOpen('../../../test.htm', 665,
>480)">Text</A>
>77: </P>
>78:...
>
>1b. Tidy-Warning-Message:
>line 76 column 13 - Warning: <a> escaping malformed URI reference
>
>1c. Tidy's-Output:
>74:...
>75: <P>
>76: Text <A
>HREF="javascript:parent.WindowOpen('../../../test.htm',%20665,%20480)">Text<
>/A>
>77: </P>
>78:...
>
>1d. Comment:
>In line 76 of the HTML-Source Tidy interpret the javascript code as an URI
>reference. Further Tidy's-HTML-Output-File is false (%20 instead of spaces).
>
>
>Please let me know when the bug are fixed.
>Many thanks in advance.
>
>JH
Received on Monday, 2 December 2002 12:27:41 UTC