Closed
Bug 192517
Opened 22 years ago
Closed 22 years ago
Opening a frameset in 1.3a freezes the browser.
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jc, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021213
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021213
Opening a frames-based pages displays the full frameset, but freezes composer.
Reproducible: Always
Steps to Reproduce:
1. Try to edit any framebased page
2.
3.
Actual Results:
the framed pages becomes visible, but composer freezes.
Expected Results:
Just open the "noframes" frameset page
Comment 1•22 years ago
|
||
I can't reproduce this issue when opening the url specify using the Open Web
Location command. The frameset loads in the composer window for me. Tested under
Win32 2003-02-11-08, Mach-O 2003-02-12-03, and Linux 2003-02-12-10 trunk build.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•22 years ago
|
||
With 1.3b it doesn't freeze - but it doesn't give me anything I can edit. It
just shows the frameset - hitting html source doesn't get it to show the html
source. I would have thought that going into composer (which cannot edit frames
as far as I know) should display the noframes portion of the page and allow the
html to be edited.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 3•22 years ago
|
||
Yea, you might want add some comments to
http://bugzilla.mozilla.org/show_bug.cgi?id=14156 which mentions about adding
the ability to edit framesets in Composer.
Comment 4•22 years ago
|
||
Marking WFM since I can't reproduce the crash.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•