If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Wrong clipboard content while copying pages containing IFRAMEs

RESOLVED EXPIRED

Status

()

Firefox
Shell Integration
RESOLVED EXPIRED
12 years ago
12 years ago

People

(Reporter: Andrew Fedoniouk., Unassigned)

Tracking

({conversion})

1.0 Branch
x86
Windows XP
conversion
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.40607)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

If source page (e.g. front page of http://nytimes.com) contains iframes with
alternative content like:

<iframe src="...">
  <script>...</script>
  <noscript>...</noscript>
</iframe>

and user is trying to put this content into clipboard then
the clipboard contains CF_HTML formatted text given as:

<iframe src="...">
&lt;script&gt;...&lt;/script&gt;
&lt;noscript&gt;&lt;...&lt;/noscript&gt;
</iframe>

as you may see text is wrongly escaped - it should match original.


Reproducible: Always

Steps to Reproduce:
1. open http://nytimes.com in FireFox.
2. Press Ctrl-A to select text in full.
3. Press Ctrl-C to copy it into clipboard.
4. Paste clipboard content into any UA do not supporting IFRAMEs. E.g. 
http://blocknote.net application or 
http://www.evernote.com/en/products/evernote/ application.
5. Note that non-intended iframe content appears. 

Actual Results:  
<iframe src="...">
&lt;script&gt;...&lt;/script&gt;
&lt;noscript&gt;&lt;...&lt;/noscript&gt;
</iframe>

Expected Results:  
<iframe src="...">
  <script>...</script>
  <noscript>...</noscript>
</iframe>


N/A
(Reporter)

Updated

12 years ago
Keywords: conversion
Summary: Wrong clipboard content while copying pages containing IFRAMEs → Wrong clipboard content while copying pages containing IFRAMEs
Version: unspecified → 1.0 Branch
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.