Closed
Bug 73799
Opened 24 years ago
Closed 2 years ago
can't View | HTML Source on page with <iframe> tag
Categories
(Core :: DOM: Editor, defect, P5)
Core
DOM: Editor
Tracking
()
RESOLVED
INCOMPLETE
mozilla1.5alpha
People
(Reporter: sujay, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [html])
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.
*** Bug 73800 has been marked as a duplicate of this bug. ***
Comment 2•24 years ago
|
||
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?
Assignee: beppe → sfraser
Priority: -- → P3
Whiteboard: [html]
Target Milestone: --- → mozilla1.0
Comment 3•24 years ago
|
||
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•24 years ago
|
||
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•23 years ago
|
||
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
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•23 years ago
|
||
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•23 years ago
|
||
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)
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 9•23 years ago
|
||
removing myself from the cc list
Comment 10•23 years ago
|
||
Pre-sabbatical bug triage.
Target Milestone: mozilla1.0.1 → mozilla1.2alpha
Comment 11•22 years ago
|
||
Typing in the URL address showed a "The Page Cannot Be Displayed" Error. Keep
checking to see if this still exist.
Updated•22 years ago
|
Target Milestone: mozilla1.2alpha → mozilla1.5alpha
Comment 12•20 years ago
|
||
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.
Updated•20 years ago
|
Assignee: sfraser_bugs → mozeditor
QA Contact: sujay → bugzilla
Updated•18 years ago
|
QA Contact: bugzilla → editor
Updated•18 years ago
|
Assignee: mozeditor → nobody
Comment 13•4 years ago
|
||
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.
Severity: normal → S4
Priority: P3 → P5
Comment 14•2 years ago
|
||
Page no longer active
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•