127386 - opening recent Composer page from ejected floppy disk involves too many dialogues and closes Composer

Status: VERIFIED DUPLICATE of bug 142664

(Core Graveyard :: File Handling, defect)

Description

[Pete Boyd]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8+)
Gecko/20020221
BuildID:    2002022103

trying to open a file from a non-existant floppy disk using via Composer's
Recent Pages option involves trying to access the disk 4 times, thus a user has
3 redundant dialogues to dispel.
if this was a missing file on a hard disk, Mozilla only presents the dialogue in
step 12; with a floppy disk I'd expect just step 6 and 12

Reproducible: Always
Steps to Reproduce:
1. with the browser window open, choose Tasks -> Composer
2. open a recently used document that was on floppy disk with File -> Recent
Pages, without the floppy disk in the drive
3. Mozilla reports "There is no disk in the drive..."
4. choose Cancel


Actual Results:
5. focus switches back to the Navigator window
6. Mozilla reports "There is no disk in the drive..."
7. choose Cancel
8. Mozilla reports "There is no disk in the drive..."
9. choose Cancel
10. Mozilla reports "There is no disk in the drive..." 
11. choose Cancel
12. Mozilla reports "The file /A:/..."
13. Composer closes and you're back at the Navigator window

Expected Results:  after step 4, return to blank Composer window

if using Modern skin for this procedure, the "There is no disk in the drive..."
dialogues are in Classic skin whereas the "The file /A:/..." in step 12 is in Modern

Comment 1

[Kathleen :Brade]

reassign to new placeholder

Comment 2

[Robin Monks]

More "failed to access no existant drive" bugs are comming.  And this is the
oldest available bug.

Comment 3

[Robin Monks]

*** Bug 142664 has been marked as a duplicate of this bug. ***

Comment 4

[Michael Lefevre]

reassigning to default owner of new component

I'm not sure this is the best bug to dupe these to - that other bug has a bunch
of votes and ccs, a bunch of dupes, and more information about the problem...

Comment 5

[sairuh (rarely reading bugmail)]

I agree with Michael --even though this one is older, it should prolly be dup'd
against 142664 because that one has more dups/votes.

Comment 6

[timeless]

se: it hardly matters, whichever bug it is, it will be a graveyard. i am
probably going to be the person fixing the bug and i will not do it in any bug
which has end users volunteering their opinions. just let robin dupe them
together and we'll inform everyone when it's fixed.

as to information, that too doesn't matter, whichever bug is picked it will be a
graveyard and not for development.

Comment 7

[WADA:World Anti-bad-Duping Agency]

Closing this bug as DUP of Bug 142664(revert DUP chain), with adding "same
problem on Composer" in it.

*** This bug has been marked as a duplicate of 142664 ***