73799 - can't View | HTML Source on page with <iframe> tag

Status: RESOLVED INCOMPLETE

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

Description

[sujay]

using 3/27 build of netscape

1) launch netscape
2) jump to the URL above (this page has the <iframe> tag)
3) File | Edit Page
4) View | HTML Source(in composer)

it doesn't work.

workaround is to click on HTML source tab on bottom toolbar.

Comment 1

[sujay]

*** Bug 73800 has been marked as a duplicate of this bug. ***

Comment 2

[rubydoo123]

using the build from 2001032904 on win98, when the file is initially 
brought into the editor, focus is not set in the document, once the 
focus is set, selecting View|Source works fine

Simon, didn't you do some wirk with frame/iframe?

Comment 3

[Simon Fraser [no longer active]]

Editor does not currently behave correctly on pages with <iframe> tags; we should 
block these the way we do with framesets.

This will work after embedding stuff lands.

Comment 4

[[e-mail]]

Simon Fraser wrote:

> Editor does not currently behave correctly on pages with <iframe> tags;
> we should block these the way we do with framesets.

Surely iframe properties (such as height, width and src) should have their own
property editor, with the additional option to edit the referred document in its
own window.

Comment 5

[TucsonTester2]

In regards to this issue I have found that if you use the file|edit page command 
I can view the source with no problem, but if I select all on a page with 
Iframes and copy it into a new composer page, I get the error message of:

"Composer cannot edit HTML framesets, or pages with inline frames. For 
framesets, try editing the page for each frame separately. For pages with 
Iframes, save a copy of the page and remove the <iframe> tag."

This was done on win98se with QArev:2001090303

URL used: http://everquest.station.sony.com/

Step used:
1. open website
2. used the File|Edit page command
3. change from normal to source to tag to preview and back again
4. back to website in browser
5. select all and copy
6. open new composer window
7. paste in website
8. change from normal to source to preview to tag and back
9. should get error message
9. should get error message

Comment 6

[Manoj]

Using M0.9.4 downloaded on September 14 2001. Bulid id: 20010913
This bug still exists, I did the following to reproduce it and it crashed Mozilla:
OS: W2K

1. Visit http://timesofindia.indiatimes.com
2. Click View Source
3. In Source window, type Ctrl+E
4. Page opens in Composer but complains about inability to edit pages with
<iframe> tag and then crashes Mozilla

Comment 7

[shrirang khanzode]

yep, confirmed the crash on my NT 0917 branch :
Stack :
Stack Trace

PresShell::UnsuppressAndInvalidate 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 4610] 
PresShell::ProcessReflowCommands 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5998] 
ReflowEvent::HandleEvent 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5771] 
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591] 
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, 
line 524] 
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 
1072] 

Comment 8

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 9

[rubydoo123]

removing myself from the cc list

Comment 10

[Simon Fraser [no longer active]]

Pre-sabbatical bug triage.

Comment 11

[Sam J. Fleet]

Typing in the URL address showed a "The Page Cannot Be Displayed" Error.  Keep 
checking to see if this still exist.

Comment 12

[Gangadhar NPK]

User Agent:
Mozilla 1.7
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616

Opened the URL and tried to edit the http://timesofindia.indiatimes.com.
*Can* edit the page. There is *no* crash.
Reported Bug:
  A crash occurs when editing a page with an <iframe> element
Observed result:
  No crash occurs.

Comment 13

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Comment 14

[u597032]

Page no longer active