246926 - Mozilla fails with href when this dont closes quotations marks in the same line.

Status: VERIFIED INVALID

(SeaMonkey :: General, defect)

Description

[hamacker]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.6) Gecko/20040520
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.6) Gecko/20040520

Mozilla fails with href when this dont closes quotations marks in the same line.
I study the problem and arrived the following conclusion, when I use this :
href='loadmodule.php?module=articles   <=== first line
 ' ">  <=== next line
then fails,ie. when you click make nothing, the reasion is that I dont close
quote in same line. To correct/patch this problem :
href='loadmodule.php?module=articles' ">  <=== close in same line
Others browsers konqueror, IE, ... dont have this bug.

I tested in mozilla 1.3 (old), 1.6 (last) and firefox 0.9(new).
I will attached html example that the first 3 options fails and next 3 options
are OK to be.


Reproducible: Always
Steps to Reproduce:
1.See attached file.
2.
3.

Actual Results:  
You click on object and wait, wait, wait and none, no error message, no any
message, you still wait, and nothing ocours.

Expected Results:  
Fail message (404 error) or jump to link.

where can i attach file ?

Comment 1

[hamacker]

Attachment: html file that show error 3 links fails and 3 links OK.

All version win32/linux was tested and this bug exist at all.

Comment 2

[Tim Meader]

Personally, I would hardly call this a "bug". The HTML you are showing is
GLARINGLY wrong. That being said, I suppose the parser for URL's (if there is
such a component) can be given the extra ability to parse from the open quote to
the close quote, ignoring all whitespace.

Comment 3

[Tim Meader]

You need to be more clear in what you are describing though. The line wraps you
are testing a with are not based in the "a href" line like you said in the bug
description. Your examples are all based on the window.location.href property.
Which is it?

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

Error: unterminated string literal
Source Code:
window.location.href='index.php

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

quote from ecma-262:
" A 'LineTerminator' character cannot appear in a string literal, even if
preceded by a backslash \. "
(thanks, Silver)

this bug is invalid.

Comment 6

[hamacker]

sorry my poor english.
theses pages with unterminated quoted (in same line) was create by PHPNuke module.
I agree you that bug is unconvention, but HTML does not need terminator quote in
same line. 
So many programs written in PHP pre-process source code (users type in with
different languages/accent) and output (sometimes parse error) in another way
and some times create html with bizzarre quote.
Note that wrong window.href will blocks next correct href.
            \<li
 onmouseover="this.style.background='#fdffa6'"
 onmouseout="this.style.background='#D3F5D0'"
 onclick="window.location.href='index.php
 ' "\>  \<== unterminate string error
            \<a href="index.php"\>Start Here\</a\> <== will be block too
            \</li\>
The line \<a href="index.php"\>Start Here\</a\> is written correct but dont run
because window.href is unterminated string.

To me, its a bug.
In my option (can I be wrong) window.href with parse error (unterminate quote in
same line) can not block a real and correct href follows. And if exists a
sintaxe error then play message, but wait for anything...

If you need to more test, I am here ! :P

Comment 7

[Christian :Biesinger (don't email me, ping me on IRC)]

(In reply to comment #6)
> I agree you that bug is unconvention, but HTML does not need terminator quote in
> same line. 

well javascript does. but cc'ing some people who may have an opinion.

Comment 8

[Brendan Eich [:brendan]]

What's to discuss?  This is just invalid content, generated from a server setup
that needs to be fixed.

/be

Comment 9

[hamacker]

Why this bug ticket are mark as INVALID ?
I did test again with the last version of mozilla and this bug disapear.
So I think that this bugticket will be changed INVALID to RESOLVED.