Closed Bug 68168 Opened 25 years ago Closed 24 years ago

Selecting File|Open File Location with a frameset allows page in editor

Categories

(SeaMonkey :: Composer, defect, P2)

Product:
SeaMonkey
Component:
Composer
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla1.0

People

(Reporter: tapio.markula, Unassigned)

Details

using framesets might lead to un-framed page, where can't go back to the frameset http://www.nic.fi/~tapio1/Yleiset - I got them work also in Mozilla 0.7!
please provide more detailed steps how to reproduce the problem...
Is this supposed to be an editor bug? if so, is the problem that if you load a frameset document in editor the editor will convert it to a regular document and throw away the <frameset> and <frame> tags?
One more question. What DTD are you using for your frameset?
That link uses: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">
If you use a link on that page, his menu is gone. That should be the problem i guess.
If you display the pages in the current build (2/9/01) it renders fine in the browser, if you select to edit the page from File|Edit Page, a warning dialog is displayed telling the user that editing framesets is not supported and closes the edit session. If you open Composer and select File|Open File Location, it opens the file in the Composer window in a browse mode and not in an edit mode. changing summary to what I think the problem is meant to be assigning to sfraser -- Simon, shouldn't the File|Open File Location also catch that this is a frameset?
Assignee: beppe → sfraser
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: a frameset problem → Selecting File|Open File Location with a frameset allows page in editor
It should detect the frameset in that second case too. I've no idea why it would not.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
Priority: -- → P2
moving to 1.0
Target Milestone: mozilla0.9.1 → mozilla1.0
-> editor owners
Assignee: sfraser → kin
Status: ASSIGNED → NEW
-->composer
Assignee: kin → syd
Component: Editor: Core → Editor: Composer
OS: other → All
Hardware: Other → All
I got the dialog saying you can't edit this when I tried opening from composer, which contradicts beppe's report and suggests this bug is fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Works For Me as well - marking Verified
Status: RESOLVED → VERIFIED
reassign bugs in case they are later reopened
Assignee: syd → composer
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.