From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a) Gecko/20020610 BuildID: 2002061108 When linking within a frameset environment to a local file via file://, this file will not be opened/displayed in the frame assigned for display. Also the link is not displayed when not target frame or target="_top" is defined. One does not get any error message in the case the file does not exist. Opening the link into a new window/tab via the right-click menu does not work either. Opening such a link in a new window seems to work correctly _only_ on middle-click. Basic demonstration on http://www.astro.uni-bonn.de/~marggraf/test/ Reproducible: Always Steps to Reproduce: 1. Go to the URL I stated above. 2. Play with the links and see (hopefully). Actual Results: The 3rd link on that test page will not open into the lower frame. It will not open on "Open link in new tab/window" from the menu. It will open in a new window/tab on middle-click only. Expected Results: The 3rd link on that test page opens into the lower frame.
correcting URL to make it absolute...
RESOLVED/DUPE. *** This bug has been marked as a duplicate of 122022 ***
reporter: can you VERIFY if you got the pref to work or saved the file to local disk and got it to work?
I'm not sure wheter I get your request correctly. Please correct me if it's not what you wanted to know. What DOES definitely WORK (reproduced in 1.1b, build 2002072204) is a mouse middle-click on the file:// link, with "Open tab on middle-click" activated in the prefs. The file:// link is then opened and displayed in a new tab. This behaviour SHOULD be disabled for security reasons, as I understand (see also bug #151491). Saving the file:// link target to disk via the left-click menu does also work (as it should be, I guess). All other ways of opening/displaying the file:// link are disabled, as far as I know.
*** This bug has been marked as a duplicate of 84128 ***
Yep, I agree that it's rather a dupe of 84128. For the protocol: I get the expected security error ("content at ... may not load or link to file:///..."), and an "error: uncaught exception: Load of file://etc/issue denied." So let's wait for 84128 to be solved in some clean way.