287445 - URL references (#) do not work in file URLs when run from outside

Status: RESOLVED WORKSFORME

(Firefox :: File Handling, defect)

Description

[Trejkaz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

If I run a file:/// URL through Windows' "Run" dialog, the #reference portion of
the URL is stripped by Firefox, resulting in the page starting at the top
instead of from the desired anchor.


Reproducible: Always

Steps to Reproduce:
1. Create a dummy test file, I'll call it C:\test\test.html... it doesn't have
to be anything special, any HTML will be fine.
2. Enter Firefox, type "file:///c:/test/test.html#anchor" in the address bar and
hit enter (this step works fine, and is for comparison.)
3. Go to the Run dialog (either via Win-R or via the Start Menu), type
"file:///c:/test/test.html#anchor" and hit enter.

Actual Results:  
Firefox opens a new tab with "file:///c:/test/test.html" in the address bar.


Expected Results:  
The address bar should be "file:///c:/test/test.html#anchor", and Firefox should
have scrolled to the element with the specified ID.

Internet Explorer doesn't suffer the same problem, so the issue must be either
in Firefox itself, or perhaps in the remote sending of the URL to the existing
instance.

Comment 1

[OstGote!]

related to Bug 151850

Comment 2

[Trejkaz]

I saw that other bug and thought it might be the same issue, but the symptoms
are fairly different so I opened a new one anyway.  In the other bug, entering
the URL directly into the box does, at least, maintain the # in the box.  So
really, the underlying problem in the other bug is user error... they should
have escaped the # to make it something other than a reference.

But in the case of this bug, the # and everything after it is being stripped off
before the string even gets into the URL box.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Trejkaz]

Still present in Firefox 1.0.7 and Firefox 1.5 Beta 1 on Windows.

Comment 5

[ptmunshi]

I too experience the same problem. I create an html file with a '#' in the filename, say 'foo#.htm'. When I try to open the file in Firefox, the browser comes up with could not find the file. However, IE shows the file correctly.

Comment 6

[Nicholas gully]

I still get this error in firefox 1.5.0.6, especially when a windows program trys to load a local URL into a browser via ShellExecute() API call.

Comment 7

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 8

[Trejkaz]

Confirming that this has been fixed at some point.  Current version works as expected.

Setting status........to maybe what it should be, although "fixed" might be more accurate, we no longer know *when* it was fixed. :|

Comment 9

[Tyler Downer [He/Him]]

WFM is appropriate, there is no specific patch we can point to that fixed this.