Open
Bug 82811
Opened 20 years ago
Updated 3 years ago
WS work needs extending to HTML Copy/Paste
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
NEW
Future
People
(Reporter: mozeditor, Unassigned)
References
Details
(Whiteboard: [ws])
All the whitespace handling work I landed for moz091 needs to be extended to include html copy/paste. This will be a bit tricky because the copy code lives in layout, but the ws calcualtion code lives in editor. I'll attach a test case in a bit.
Comment 1•20 years ago
|
||
Joe, I'm moving this out to 1.0, since it sounds like it will entail quite a bit of work
Priority: -- → P2
Target Milestone: --- → mozilla1.0
Updated•20 years ago
|
Keywords: correctness
Whiteboard: [ws]
Comment 2•20 years ago
|
||
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)
Target Milestone: mozilla1.0 → mozilla1.0.1
| Reporter | ||
Comment 3•19 years ago
|
||
The trunk is the wave of the future!
Target Milestone: mozilla1.0.1 → mozilla1.1beta
| Reporter | ||
Comment 4•19 years ago
|
||
The days of having a half dozen milestones out in front of us to divide bugs between seem to be gone, though I dont know why. Lumping everything together as far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.1beta → mozilla1.2beta
| Reporter | ||
Comment 5•19 years ago
|
||
migrating milestones now that there are more available. i'll pull these back as I work on them
Target Milestone: mozilla1.2beta → mozilla1.4beta
| Reporter | ||
Comment 6•19 years ago
|
||
*** Bug 157379 has been marked as a duplicate of this bug. ***
Comment 7•18 years ago
|
||
Can someone explain why the last dupe is correct? What does the editor have to do with marking some text in the browser and pasting it to any other application? pi
Comment 8•18 years ago
|
||
I'd really appreciate an answer on my last question. I doubt the dupe. The problem in bug 157379. is much newer than this bug. pi
Comment 9•18 years ago
|
||
Hm, for over a year nobody besides me (with an unanswered question) has written about this. I still don't understand how a problem which showed up later than this bug can be a dupe. Anyhow, what is the future to this, the target is history. pi
Comment 10•16 years ago
|
||
Can someone confirm Bug 239693 is a dupe of this bug or not? I still have the problem described in Bug 239693 with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050411 Firefox/1.0+
Target Milestone: mozilla1.4beta → Future
Updated•14 years ago
|
QA Contact: sujay → editor
Updated•14 years ago
|
Assignee: mozeditor → nobody
Comment 11•3 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•