Closed Bug 361492 Opened 19 years ago Closed 19 years ago

Frames support

Categories

(SeaMonkey :: Composer, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ric.almeida, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Composer should support frames. I believe it even should include "models" of some framesets for people to use, but at least it shouldn't remove the code made by hand... Reproducible: Always Steps to Reproduce: 1.Start a new web page in Source mode 2.Remove the body and put a frameset 3.Put in Normal mode Actual Results: Frameset is removed and replaced with an empty body Expected Results: Frameset isn't removed and show the frames within the page I've put the severity in major as user data is lost...
We're not going to support frames. frames are evil. Old issue resolved forever.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
I can understand a decision to not support frames. But I also believe that erasing user code is a bad option. Since you don't wanna support frames a midterm solution would be not allow the user to go to normal mode if a page has frames, showing him a message like: "Frames are not supported. Pages with frames can only be edited in Source mode"
You need to log in before you can comment on or make changes to this bug.