Our current dropping code for navigator is too simplistic; we just load the URL regardless of where you drop it. Ideally, dropping an URL into a frame would load the URL in that frame only.
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: --- → mozilla1.0
this is actually a pet-peeve of mine in N4.x - I want to just drop anywhere in the window and have it load as a toplevel document. for the sake of 4.x compatibility, how about we do what this bug says and make shift-drag load it as a toplevel document?
Hm...IE loads it as a top-level document regardless. And if we do what this bug says, it will basically be impossible for the user (who won't know about shift+drag) to drag a link into a frameset and load it as a top-level document. And it could be hard for the user to tell if frames even exist on some pages. So maybe we should actually make loading in the frame the special (and thus, requiring the modifier) case? Matthew, what do you think? Maybe we've found a use for the suggestion in bug 25742?
Since you filed this bug, Blake, perhaps you could explain what use opening a dropped link in a single frame could *ever* have, with modifier or without? I can't think of any case where it wouldn't just be annoying, or confusing, or both. 4.x for Mac incorrectly shows drop feedback on only the target frame, but still replaces the entire frameset with the dropped link. And no, there are *no* legitimate uses for bug 25742. Ever. :-)
I use it often, when there's (for example) a navigation bar on the left that I want to keep, or just whenever I want to keep content on the left side while reading something new on the right.
You, sir, are the one percent case. If you want to keep something on the left while reading something new on the right, open a new window.
Priority: P2 → P4
I still suggest wontfix.
If you really don't care, then take yourself off the CC for this bug.
I do care. I care about when users will drag an icon into a Navigator window, and are confused/annoyed to find that the dragged document has only loaded in part of the window just because the previous page happened to be using (possibly invisible) frames.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.