143190 - Can't drag&drop HTML files onto Composer title bar to be opened for editing

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[[e-mail]]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0+)
Gecko/20020505
BuildID:    2002050508

You can not drop dragged files onto composer and have it open them for editing.
files can only be dropped into the main editing area and then it puts a link to
the file. This behaviour is fine but you need to add the ability to drop files
onto the title bar which then opens the file.

Reproducible: Always
Steps to Reproduce:
1. drop a file onto composer
2.
3.

Comment 1

[R.K.Aa.]

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

Comment 2

[sujay]

verified.

Comment 3

[Kathleen :Brade]

reassign in case bugs are later reopened

Comment 4

[Prognathous]

Re-opening. This is *not* a dupe of Bug 59574.

- Bug 59574 requests that HTML files dragged into the editable *content area*
will be opened instead of linked. This is definitely an INVALID request.
- This bug, however, specifically asks to keep the current behavior, but to add
support for dragging HTML files to the *title bar*. This is not only a valid
request, it is the exact behavior of standard Windows editors such as Wordpad
and Microsoft Word - they both support opening files by dragging to the title
bar, but not by dragging to the content area.

Prog.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
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

Comment 6

[Robert Kaiser]

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