Closed Bug 105975 Opened 23 years ago Closed 22 years ago

problem of Mail reader recognition URL doublespace following URL

Categories

(Core :: Internationalization, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Future

People

(Reporter: aqua_magius, Assigned: nhottanscp)

Details

(Keywords: intl)

for example)
http://www.jp.uo.com/¡¡¡¡Here is
                      <- double space(0x8140)

if double space exists following URL, Mailer and browser recognize for URL it.
Component: Browser-General → Internationalization
Confirmed with 2001101909/Win2k.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Confirmed with 2001102203/Win2k.

No, this isn't the same as bug 104693.
2001101909/Win2k doesn't have bug 104693, but have this bug.
->reassign
Assignee: asa → yokoyama
QA Contact: doronr → teruko
nhotta/ftang: how should we handle in case of double-byte space in URL? 
It is usually used as same as normal space.
but ISO-2022 Code 0x2121 or EUC 0xa1a1 code would not be used in URL.

We want not to the product recognize double space as URL.
Status: NEW → ASSIGNED
Double-byte space in URL has to be escaped. But I think this bug is asking
something else. Is this asking double-byte space to be treated as a URL delimiter?

In RFC 2396, it mentioned about delimiting URI by whitespace. That has no
mention about double-byte space. I think it is restricted for ASCII whitespace.

http://www.ietf.org/rfc/rfc2396.txt
E. Recommendations for Delimiting URI in Context


Anyway, in HTML document, using 'HREF' should prevent this ambiguity, instead of
expecting browser to parse and recognize the link.


Keywords: intl
could someone make a clear reproduce procedure? 
Where will you see this problem ? in the URL bar ?
HREF inside a HTML ?
Bugzilla ?
Plese select Euc-Japanese.

http://www.jp.uo.com/¡¡¡¡Here is

Clicked this link, I want to jump to "http://www.jp.uo.com/"
But Mozilla will go to "http://www.jp.uo.com/¡¡¡¡Here"
QA Contact: teruko → ruixu
well... in your example, the code which turn the text into URL is the bugzilla.
It is NOT Browser which recognize it as part of the link, it is the bugzilla
turn that into a link. not sure about the case of mail. 
Assignee: yokoyama → nhotta
Status: ASSIGNED → NEW
Removed "Browser" from the summary.
I think the link parser for mail is Ben's.
Assignee: nhotta → ben.bucksch
Summary: problem of Mail reader&Browser recognition URL doublespace following URL → problem of Mail reader recognition URL doublespace following URL
> We want not to the product recognize double space as URL.

Yuki, are you shipping a custom product based on Mozilla?

nhotta, ftang,
This is the same problem as in bug 123326 (closed as wontfix for now). I use
ncCRT:IsAsciiSpace() in my code. It is the task of that function to either
recognize the doublespace as space or not. My code does not care.

So, the real fix for this bug and the other one is that nsCRT is I18Ned.
Alternatively, close them as WONTFIX.

Reassign to nhotta.
Assignee: ben.bucksch → nhotta
Target Milestone: --- → Future
Status: NEW → ASSIGNED
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9) Gecko/20020311
There is same problem.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
I've reconsidered this bug and believes this should be resolved invalid.
Double-byte space isn't space.
You need to log in before you can comment on or make changes to this bug.