Closed
Bug 133728
Opened 23 years ago
Closed 23 years ago
Copying from a nested <li> doesn't send correct data to clipboard
Categories
(Core :: DOM: Editor, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: bugzilla3, Assigned: mozeditor)
Details
Attachments
(1 file)
353 bytes,
text/html
|
Details |
Build 2002032603, Win2K.
Copying from nested (either ordered or unordered) lists is unusable (clipboard
content doesn't resemble to the copied text).I saw it first on mozilla.org
status updates (copying a non-linked bug number from there doesn't work).
Following testcase (valid html, see attachment) reproduces the issue:
<ul>
<li>1. This text can be copied
<ul>
<li>2. This text cannot</li>
</ul>
</li>
</ul>
Steps to reproduce:
1. Open the testcase (or above url)
2. Copy some text from inside a nested list
3. Paste into any other Mozilla textfield (e.g. url bar) or external application
Actual results: Only a "#" is pasted (for an unordered list)
Expected results: Copied text is pasted
Assignee | ||
Comment 3•23 years ago
|
||
can anyone else see this? This worksforme from my own debug build of 5am pst on
the 26th
Still doesn't work on 2002032708, Win2K (using context menu or keyboard).
remember when you copy text from a list you're probably
gonna get more than the text in your buffer...you'll also
get list structure, right Joe? that could be what is
causing the "#" to be showing up in the buffer...
>that could be what is causing the "#" to be showing up in the buffer...
Definitely agree. that is why when you copy from an nested ordered list (<ol>),
you get the list numbering prefixes, i.e. "1." or "2." etc instead of a "#".
Sorry for not being clear on that.
Assignee | ||
Comment 8•23 years ago
|
||
fixed everywhere (branch and trunk) by earlier work
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
The "#" character is still present but the rest of the bug is indeed fixed.
Should we reopen because of "#" or that should be filed separately?
Comment 10•23 years ago
|
||
Dipa, file a new bug for the "#" and mark this bug verified...
thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•