Closed
Bug 5507
Opened 25 years ago
Closed 25 years ago
selecting file | open creates new window
Categories
(Core Graveyard :: Tracking, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: cpratt, Assigned: german)
Details
build id: 1999042608
platforms this happens on: windows nt, mac os 8.5.1
(linux crashes before opening the file)
to reproduce this, select open from the file menu and open a local file. result:
the file opens, but in a new window.
expected result: the file opens in the current browser window.
The spec is ambiguous about how this is supposed to work. My understanding is
that opening a new window is how it's supposed to work. I'm re-assigning to
German. We need further guidance on how URLs are loaded versus files and
whether the user can choose to open in the current window or a new one.
for the record, legacy Netscape browsers and IE all open local files in the
spawning window, ie the window from which file | open was selected. given that
this behavior is expected by (I assume) nearly all users, we should probably
keep it in 5.0...
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
I'm reopening this bug in hopes of getting the UI team to implement File | Open
in the same manner it's implemented in previous versions of Communicator and in
current versions of IE.
Have you considered doing something like this?
The File menu can have two items: Open File and Open Location, with Ctrl-O and
Ctrl-L shortcuts. Both commands have a checkbox in the dialog asking you if you
want to open the location in a new window (the checkbox is an implicit pref,
keeping its state across uses). Additionally, Open File would be smart enough to
know when it's got a URL typed in it (as does current Communicator).
That would work for me. This way, everyone who's ever used IE or Communicator
experience behavior that is familiar (things open in the same window) - and
anyone who wants to open a file or URL in a new window has the option of doing
so, which is not currently available in Communicator or Win IE. It's just the
forced imposition of the new-window-behavior that I find extremely problematic,
UE-wise.
Updated•25 years ago
|
Target Milestone: M6 → M7
Comment 7•25 years ago
|
||
moving to m7
Updated•25 years ago
|
Target Milestone: M7
Comment 8•25 years ago
|
||
unsetting the target milestone so I don't have to look at this bug every
three weeks...
german, are we doing this, or no?
Moving all Apprunner bugs past and present to Other component temporarily whilst
don and I set correct component. Apprunner component will be deleted/retired
shortly.
Comment 10•25 years ago
|
||
To keep this simple bug open for 3 months is a waste of everybody's time.
Introducing pointless UI-changes is not the way to build a 'better' Netscape, is
it? Sorry to be so rude. I'm just an outsider who hates to see so many known
bugs persist. Debugging becomes useless this way, even counter-productive
because of all the duplicates. You'll slip not months but YEARS this way.
Updated•25 years ago
|
Severity: normal → enhancement
Comment 11•25 years ago
|
||
I would like to see either:
1. A "Open in new window" checkbox appended to the "Open File" dialog
or,
2. The "Open File" and "Open Location" dialogs integrated, as they are in 4.x,
with a checkbox option for "Open in new window", along with an radio button
"Open in [composer | brower]" option.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 12•25 years ago
|
||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•