Open Bug 383864 Opened 17 years ago Updated 2 years ago

CSS formatting ignored when copying and pasting prestyled elements like lists and tables

Categories

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

x86
Windows 2000
defect

Tracking

()

UNCONFIRMED

People

(Reporter: bugzilla.mozilla.org, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4

The formatting of copied and pasted text seems to be html-element-specific and can't be influenced by CSS, thus major discrepancies (lesser ones are expected) between screen representation and the copied and pasted content arise.

Reproducible: Always

Steps to Reproduce:
1. create an unordered list or a table
2. use CSS style all elements to be display:inline
3. copy and paste the content somewhere
Actual Results:  
The copied/pasted content contained newlines, tabs etc. which represent the default formatting of the elements, but not the actually used formatting

Expected Results:  
If elements are inlined they shouldn't create newlines. C&Ping content that is represented as list (e.g. because it's semantically a list) but presented as a single line to (for example) IRC causes flooding, wasts screen real estate etc.
 The 8472 do you still see this?

Stephanie might try this shortly.
Yes,

tables and lists still insert newlines, tabs and indentation even if styled as display: inline;
Severity: normal → trivial
Is this about pasting to a plain text editor (in which case it's arguably the same as bug 492147) or to a rich text - Word/Outlook/HTML editors (bug 406488)?
Flags: needinfo?(bugzilla.mozilla.org)
Plain text
Flags: needinfo?(bugzilla.mozilla.org)

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: trivial → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.