150620 - Addresses in status bar are displayed decoded (unescaped)

Status: RESOLVED WONTFIX

(SeaMonkey :: UI Design, defect)

Description

[ingrid schall]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; de-AT; rv:1.0rc3) Gecko/20020523
BuildID:    2002052306

Hi,

Mozilla does not work taking over a string containing 
german umlauts (ה,�,צ) using the php-macro 'rawurlencode'. 
Netscape 6.1,6.2 and also IE have no problem concerning this.

example 

<?php
$text = rawurlencode('הה צצ ��');
echo "
<a
href=javascript:newWindow('./test.php?text=$text','','width=430,height=60,dependent=yes')
onClick=\"submit()\">
</a> ";

best regards 
Ingrid


-----------------------------------------------------------------------------------------
---------- enclosure: description rawurlencode -----------------------
rawurlencode

(PHP 3, PHP 4 )
rawurlencode -- URL-encode according to RFC1738
Description string rawurlencode ( string str)
Returns a string in which all non-alphanumeric characters except
-_. have been replaced with a percent (%) sign followed by two hex digits. This
is the encoding described in RFC1738 for protecting literal characters from
being interpreted as special URL delimiters, and for protecting URL's from being
mangled by transmission media with character conversions (like some email systems). 

--------------------- end manual rawurlencode ------------------------- 
-----------------------------------------------------------------------


Reproducible: Always
Steps to Reproduce:
1. editing the example 
2. 
3.

Comment 1

[Boris 'pi' Piwinger]

What does Mozilla have to do with PHP? Mozilla only gets the output.

Please provide testcase.

pi

Comment 2

[alge]

url: http://alge.nlc.no/~alge/mozbug.php
it seems like the encoded text (%E4%E4%20%F6%F6%20%FC%FC) is decoded by mozilla.
which kind of defeats the purpose of using rawurlencode().

Comment 3

[Boris 'pi' Piwinger]

I think this is intended. The link is still correct, it only displays decoded.

That would make this bug INVALID.

pi

Comment 4

[jag (Peter Annema)]

This isn't string.

darin, jst, any idea if this belongs to one of you?

Comment 5

[Darin Fisher]

cc'ing nhotta

Comment 6

[Boris 'pi' Piwinger]

*** Bug 150690 has been marked as a duplicate of this bug. ***

Comment 7

[Boris 'pi' Piwinger]

Looks like bug 60178. Dupe it there and reopen? Over to internatinalization. NEW
for a decision of QA.

pi

Comment 8

[Roy Yokoyama]

nhotta: is this intended?

Comment 9

[ingrid schall]

Hi,

it's a pity that we can't use Mozilla for our intranet solution because of this
bug. Do you think the mozilla-team will solve this problem?
We are very interested in a solution.


regards ingrid
 

Comment 10

[nhottanscp]

> url: http://alge.nlc.no/~alge/mozbug.php
> it seems like the encoded text (%E4%E4%20%F6%F6%20%FC%FC) is decoded by 
mozilla.
> which kind of defeats the purpose of using rawurlencode().

But looking at the info in the original bug report, it does not prohibit 
decoding it for UI display.
I tried http://alge.nlc.no/~alge/mozbug.php with IE 5 and IE 6, the URL was 
unescaped for status bar display.

Comment 11

[timeless]

.

Comment 12

[Boris Zbarsky [:bzbarsky]]

ingrid, how is this bug a problem for you intranet?  This bug does not affect
anything mozilla does except what it shows in the status bar...

I'm failing to see what the bug is here, frankly...

Comment 13

[Bill McGonigle (not currently reading bugmail; please contact directly)]

This is a problem when you're developing websites and you'd like to be sure the
links you build are correct.  In previous versions of Mozilla I could just
mouseover and check the status bar.  Now I have to view source and find. 
Significantly less convienient.

Comment 14

[Jesse Ruderman]

Bill: right-click, copy link location (or properties).

IE does this too.  I think it's intentional, to help international users see
where they're going.

Comment 15

[Darin Fisher]

marking WONTFIX.  mozilla purposefully decodes any escape sequence in the URL
string that corresponds to a character in the document charset or UTF-8.  this
is done as Jesse said to improve the experience for international users.  the
decoded URL string is created only for display purposes.

Comment 16

[OstGote!]

*** Bug 295521 has been marked as a duplicate of this bug. ***