Opened 13 years ago
Closed 12 years ago
#8287 closed Bug (invalid)
Internet explorer Frameset issue
| Reported by: | Keven | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | 3.2 |
| Keywords: | IE9 | Cc: |
Description
When using Internet Explorer 9 in a page within a frameset the CKeditor instance's menu bar covers the entire document and the editor area can not be seen. This is the same with FCKEditor 2.x as well which I tried as a back up. Pulled from the frameset the exact sane page works fine.
Page works in frameset under Firefox, Opera, Chrome and Safari.
Attachments (3)
Change History (8)
Changed 13 years ago by
| Attachment: | CKeditor_frameset.JPG added |
|---|
comment:1 follow-up: 2 Changed 13 years ago by
| Status: | new → pending |
|---|
I couldn't reproduce the issue.
Could I ask you to provide a sample test case file that would help reproduce the problem?
comment:2 Changed 13 years ago by
Replying to j.swiderski:
I couldn't reproduce the issue.
Could I ask you to provide a sample test case file that would help reproduce the problem?
FRAMESET: http://bcalpine.com/ck/troubleshooting/frames.html
RIGHT FRAME BY ITSELF: http://bcalpine.com/ck/troubleshooting/frame2/
Only IE9 has the issue. I find that using compatibility mode sometimes fixes it, sometimes not.
comment:3 follow-up: 5 Changed 13 years ago by
| Keywords: | IE9 added |
|---|---|
| Status: | pending → confirmed |
| Version: | 3.6.1 → 3.2 |
- Put test case files from attachment into samples folder
- Open framset.html sample.
Result: Content area is not visible.
This is because page frame2.html has no doctype thus main page is displayed in "IE9 mode" and frame2 in "quirks mode". From what I have spoken with @wwalc IE9 has problems with let's say working with more than one mode.
A workaround to the problem is to add doctype in frame2.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
or
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Issue has been reproducible from CKE 3.2
Changed 13 years ago by
| Attachment: | frameset.zip added |
|---|
comment:5 Changed 13 years ago by
Replying to j.swiderski:
Perfect solution, thank you!
I just hope someone knows a solution for my other issue http://dev.ckeditor.com/ticket/8288 and then IE users will stop complaining to me! :)
comment:6 Changed 12 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | confirmed → closed |
#9807 was marked as duplicate.
Please note that frames are dead now. If you still want to use them please note that mixing doctypes is not way to go.
After consulting this issue with my colleagues we have decided to close it with couple of guide lines (based on users’ mistakes):
- You can't use HTML5 doctype declaration for frameset. Frames are not supported in HTML5. HTML4 frameset declaration is needed here.
- Don't forget to use head section in frameset page
- Don't forget to put doctype declaration (HTML4 transitional or loose) in frame page because you will get in mixed doctypes and errors.
Please have a look attached zip file - it shows how frames should be used.
Changed 12 years ago by
| Attachment: | HowFreamesetShouldLookLike.zip added |
|---|
Shows the same page in frameset with IE on left and Chrome on right.