Closed
Bug 189071
Opened 22 years ago
Closed 22 years ago
iframe support in composer?
Categories
(SeaMonkey :: Composer, enhancement)
Tracking
(Not tracked)
People
(Reporter: k-marken, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
i had a look around but could not realy find any "bug" reports on this...
whenever i open a page with iframe support in composer it tells me to remove the
tags and then come back to edit the page. seems stopid to me as it can be coded
to just ignore the html of any source pages put into the iframe tags and just
let the person wanting to edit the page, edit the page or something similar.
why the overreaction with booting any page using iframe or frames out of
composer (and this will be 90% of any resent pages!) when composer can be coded
to just ignore the src part of the iframe tag or similary not read the hmtl code
of the page it points to or in some other way make the user able to edit the
hmtl code of the page without having to remove the (i)frame tag(s) first...
Reproducible: Always
Steps to Reproduce:
fire up any page with a iframe in composer
Actual Results:
a popup telling the user to remove the iframe tags
Expected Results:
give the user the abiltiy to edit the current page, ignoring the thml source of
the pages inside the iframe...
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 14156 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•