69550 - dropping into plaintexteditor should have can't drop cursor sometimes

Status: REOPENED

(Core :: DOM: Editor, defect, P5)

Description

[sujay]

using 2/19 build of netscape

1) launch netscape
2) launch composer
3) Debug | plaintexteditor
4) insert an object into composer(image, h. line, link, target)
5) drag that object and drop into plaintexteditor

I know plaintext editor doesn't support these objects. So we
should be showing that drop as an illegal drag drop by changing
the cursor to reflect that..Currrently the cursor feedback looks
like a legal drop..

all platforms.

Comment 1

[rubydoo123]

assigning to sfraser

Comment 2

[rubydoo123]

giving to brade

Comment 3

[Kathleen :Brade]

I have a partial fix for this bug...

Comment 4

[Kathleen :Brade]

Attachment: partial fix; check length of data before adding flavor [Checkin: Comment 7]

Comment 5

[Kathleen :Brade]

pink:  please review
Simon:  please super-review

Comment 6

[Mike Pinkerton (not reading bugmail)]

looks good, r=pink

Comment 7

[Kathleen :Brade]

I checked in this fix a few days ago

Comment 8

[sujay]

reopening...

two problem here:

1) the cursor doesn't reflect an illegal drop
2) the object doesn't get dropped in..

I wasn't sure if we decided to allow drag + drop of objects into
plaintext editor so I'm posting both issues...

Comment 9

[Kathleen :Brade]

so, if nothing appears when dropped, then we should get the other cursor and not 
let people drop stuff.

For some reason, I'm seeing the "drop" being enabled because there is unicode 
flavor on clipboard (this is by dragging an hrule from composer to plaintext 
editor).  The unicode flavor shouldn't be present if there isn't any text.  It 
appears that it is being added without any content.  :-(

Comment 10

[Syd Logan]

spam composer change

Comment 11

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 12

[Serge Gautherie (:sgautherie)]

Kathleen,
Are you still working on this ?

Comment 13

[Robert Kaiser]

Doesn't look like this is still a helpful bug in its current state, moving to INCOMPLETE for the moment.

Comment 14

[Kathleen :Brade]

Incomplete?  What part of the steps are not understood?
I'm guessing this affects Mail Compose (plain text).
I would think a better question is: Can this bug be reproduced in TBird?

Comment 15

[Robert Kaiser]

(In reply to comment #14)
> Incomplete?  What part of the steps are not understood?
> I'm guessing this affects Mail Compose (plain text).
> I would think a better question is: Can this bug be reproduced in TBird?

Kathleen, this had been without a comment for more than 6 years, then you didn't reply to a question for almost two years, so I don't see that something can be badly broken here.

That said, IMHO, Thunderbird is completely irrelevant as long as the bug is in the SeaMonkey product, the question would be if it can be reproduced in SeaMonkey 2.x, actually. And even then, I doubt this is either a SeaMonkey or a Thunderbird bug, if it still exists, it's probably a core editor thing.

Still, with over 8 years of no real activity, I'd call the bug bogus unless someone comes up and takes responsibility for it.

Comment 16

[Kathleen :Brade]

I believe my response to comment 12 was to add "helpwanted"

Sorry; I didn't notice what product this bug is assigned to.

Yes, I agree the bug will be in the core editor (not specific to SeaMonkey or Thunderbird).

I still contend that the bug is not "bogus"; instead you might say that it is irrelevant or unimportant.  I suggest resolving as WONTFIX (unless it is known that the bug can no longer be reproduced).

Comment 17

[Robert Kaiser]

I didn't say it's irrelevant or unimportant. If it still might be of value, I'm all for reopening and moving it to core/editor (whatever the exact name of the component there is), I just wanted to clean out the SeaMonkey realm from it, and stumbled over this as it was still marked ASSIGNED to you but didn't have any progress.

So, if you think it's still relevant, please REOPEN it and move it where it actually belongs nowadays - I'm all happy if action actually might happen and our software gets improved!

Comment 18

[Kathleen :Brade]

reopening; recategorizing; helpwanted still applies

Comment 19

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.