Bug 3263 - REGRESSION (1.2-2.0): XHTML Frame fails to be rendered in frameset
Summary: REGRESSION (1.2-2.0): XHTML Frame fails to be rendered in frameset
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: 412
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Eric Seidel (no email)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-03 21:38 PDT by Chris Petersen
Modified: 2005-12-26 14:08 PST (History)
0 users

See Also:

Attachments
XHTML 1.0 Frameset document that uses a .xml extension (403 bytes, text/xml)
2005-06-03 21:41 PDT, Chris Petersen 		no flags Details
XHTML 1.0 Frameset document that uses a .html extension (403 bytes, text/html)
2005-06-03 21:42 PDT, Chris Petersen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Petersen 2005-06-03 21:38:19 PDT 
Expected Results: All frames should be rendered with content
What I got: With two frames specified in a frameset, I only get one frame rendered

This problem occurs with Safari 2.0 under 10.4.1 (8B15) but not with Safari 1.2.3 under 10.3.5. Haven't 
checked  Safari 1.3 under 10.3.9.

Steps to reproduce:

1) Open attached file "frame_frameborder_0.xml" in Safari 2.0 (412)
2) Notice the first frame is rendered (apple.com) but the second frame isn't displayed
3) Now , open attached file "frame_frameborder_0.html" This is a exact copy of the previous test except 
it has a .html extention. This file is rendered with both frames properly rendered.

Perhaps there is a parser error when the file uses a .xml extension ?
Comment 1 Chris Petersen 2005-06-03 21:41:34 PDT 
Created attachment 2098 [details]
XHTML 1.0 Frameset document that uses a .xml extension
Comment 2 Chris Petersen 2005-06-03 21:42:38 PDT 
Created attachment 2099 [details]
XHTML 1.0 Frameset document that uses a .html extension
Comment 3 Chris Petersen 2005-06-07 11:45:43 PDT 
Apple Bug : <rdar://problem/4141211>
Comment 4 Daniel Udey 2005-11-09 10:14:44 PST 
This bug is confirmed in Safari 2.0.2 but works properly in ToT.