Closed Bug 43905 Opened 24 years ago Closed 14 years ago

"non-native" file:/// URL in bookmarks.html not gracefully handled

Categories

(SeaMonkey :: Bookmarks & History, defect, P3)

Product:
SeaMonkey
Component:
Bookmarks & History
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: jrgmorrison, Unassigned)

References

Details

Overview Description:

  unix/mac style 'file:///foo/bar/baz.html' bookmark URL on Windows

    or 

  windows style 'file:///c:/bar/baz.html' bookmark URL on mac/linux

  is not handled correctly in the Bookmarks menu and in Bookmark manager.

  (Note : Double clicking in the bookmark sidebar panel (for any 
  URL) currently produces the error BrowserAppCore not initialized'
   --  is there a bug already open for that?

Steps to Reproduce:

1) Manually add a URL to your bookmarks.html while the browser is 
   not running. (This is the quick way to simulate a user copying 
   over a bookmarks.html from a different OS, where that file 
   contains a native file URL as a bookmark). 

   Add this on Windows:
      <DT><A HREF="file:///foo/bar/baz.html">file url</A>
        To be clear, this is a file URL that lacks a drive letter 
        (e.g., 'C:' or 'C|')

   Add this on Mac/Linux:
      <DT><A HREF="file:///C:/bar/baz.html">file url</A>


2) start the browser; open the top-level bookmarks menu : 

3) click on the text 'file url'

Actual Results:

 WINDOWS 2000062608
   a) url bar updates to file://///foo/bar/baz/html
   b) message in the console "Error loading URL file://///foo/bar/baz/html"
   c) the Unknown File Type dialog pops up : "You are about to download a 
      file of type text/html. This file is unrecognized by Netscape" ... etc.
  
 LINUX 20000626nn
   a) url bar updates to file:///C:/bar/baz.html
   b) an empty directory.xul instance is brought up in the current browser 
window
  
 MAC 20000626nn
   a) url bar updates to file:///[C:]/bar/baz.html
   b) the Unknown File Type dialog pops up : "You are about to download a 
      file of type text/html. This file is unrecognized by Netscape" ... etc.
  
Expected Results:

  If the URL can't be resolved, then an alert dialog stating the problem 
  should be thrown up.

Additional Information:

  There is a second consequence of having a windows file:// url in a 
  bookmarks.html file on mac/linux : it causes subfolders in the menu of 
  bookmarks to be displayed as non-folders (as simple bookmarks).
  I'm filing that bug in a moment (but that's RDF stuff, I think).
m19
Target Milestone: --- → M19
Reassigning 79 Bookmarks bugs to Ben.  I was told this was going to be done 
shortly about two months ago, but it clearly hasn't been.  I think that's long 
enough for all these bugs to remain assigned to nobody.

Feel free to filter all this spam into the trashcan by looking for this string 
in the message body: ducksgoquack
Assignee: slamm → ben
Netscape Nav triage team: this is not a Netscape beta stopper.
Status: NEW → RESOLVED
Closed: 24 years ago
Keywords: nsbeta1-
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
It's not INVALID. There is nothing contrived about someone moving a file
'bookmarks.html' from one OS to another and expecting it to work. 
john is correct and one day, far away, when we're once again able to share profiles across
machines this will be the number one bug.
OS: Windows 95 → All
Hardware: PC → All
Status: REOPENED → ASSIGNED
Marking nsbeta1- bugs as future to get off the radar
Target Milestone: --- → Future
*** Bug 59416 has been marked as a duplicate of this bug. ***
Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter 
email notifications caused by this by searching for 'ilikegoats'.
Assignee: ben → pchen
Status: ASSIGNED → NEW
mass reassign of pchen bookmark bugs to ben
Assignee: pchen → ben
I don't think that this bug is valid !

file:///C:/bar/baz.html could be also file:///D:/bar/baz.html
There is no way to know whow the link should be corrected.
matti: well, the behaviors john reported don't exactly make much sense.  we
should try to do something sane when encountering URLs to resources that do not
exist.  since this bug is rather old, it would be good to check what our current
behavior is.  maybe we get the error handling right now ;-)
Darin: You mean non working error handling like bug 98682 ?
matti: well... i wasn't thinking so much about UNC paths, but maybe... given
that windows reportedly treats 'file:///foo/bar/baz.html' as a UNC file path. 
that bug probably is related.  thx!
Well, on win2k, a bookmark to 'file:///foo/bar/baz.html' just silently does 
nothing, which is fairly graceful (although perhaps without feedback a little
surprising). Haven't checked the other platforms, but this bug, while valid,
isn't a major issue.
Product: Browser → Seamonkey
Assignee: bugs → nobody
QA Contact: claudius → bookmarks
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 14 years ago
Resolution: --- → EXPIRED
Non-working file: bookmark locations result in "File not found" error page, which seems rather sane => WFM.
Resolution: EXPIRED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.