Closed Bug 26093 Opened 26 years ago Closed 25 years ago

Whitespace is not being carried in cut and paste operations

Categories

(Core :: Layout: Form Controls, defect, P3)

Product:
Core
Component:
Layout: Form Controls
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 47309

People

(Reporter: Scott.Springer, Assigned: akkzilla)

References

(
URL
)

Details

(Whiteboard: [rtm NEED INFO])

When submitting my last bug I realized that whitespace was collapsing when I cut and paste within the textarea element. I didn't try doing it between different applications, and I didn't try it between different form elements. When the paste is done, a single space is kept, but if I attempted to use whitespace to get a visual effect (wonderful ASCII art) the extra space was lost. I have no idea whether or not the space is collapsed or not when the data is submitted.
Reassigning to Steve.
Assignee: karnaze → buster
the problem seems to be on the copy side of the equation. I copy from a textarea and paste into notepad (on Windows), and my spaces have been collapsed. assigning to akkana. Akkana, up to you to assign a real priority and milestone.
Assignee: buster → akkana
Severity: minor → normal
Accepting. To reproduce this, I view this bug page, and type "a b<ret><ret>c" in the "Additional Comments" field, select and copy it all, and paste into plaintext. The two returns come through but the extra whitespace doesn't. Setting to M15 (i.e. post beta), but willing to listen to arguments as to why it should be fixed sooner.
Status: NEW → ASSIGNED
OS: Windows NT → All
Hardware: PC → All
Target Milestone: M15
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Spaces are collapsing again... Reopening. Tested on Windows 98 build 2000-09-22-08-M18 and Linux RedHat 6.2 build 2000-09-19-21-M18
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updating QA contact.
QA Contact: ckritzer → bsharma
Priority: P3 → P2
moving to m19 to get on the radar
Target Milestone: M15 → M19
Dependant on dom serializers. With the current XIF model, now that ender lite doesn't preserve wrapping information in the body, it would take a redesign to get this information through to the output system. With serializers, it should be pretty easy.
Status: REOPENED → ASSIGNED
Depends on: 50742
rtm need info
Keywords: rtm
Whiteboard: [rtm NEED INFO]
P3. Will NOXIF fix this, or does it need extra work? If the latter, is a candidate for rtm-.
Priority: P2 → P3
The dependendancy is because noxif makes it possible to fix this without architectural changes (the reopen was caused by ender lite, since pre and wrap column can no longer be passed in the body to the output system, so they end up being ignored). Not only does noxif not fix this by itself, but it makes it worse: the double whitespace between a and b is still not copied, but in addition, '\n\nc' is not copied at all; only the first line is. This may be related to the other known problems with copying across breaks. Cc'ing Joe and jst.
Marking this a dup of 47309 (because that bug has slightly more info in it). They cover the same problem. *** This bug has been marked as a duplicate of 47309 ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
Sorry for the spam! But apparently all these closed bugs need to have their target milestones changed since M19 and M20 are going away. Since they're allready closed, I'm choosing M18.
Target Milestone: M19 → M18
You need to log in before you can comment on or make changes to this bug.