Bug 3263

Summary: REGRESSION (1.2-2.0): XHTML Frame fails to be rendered in frameset
Product: WebKit Reporter: Chris Petersen <c.petersen87>
Component: FramesAssignee: Eric Seidel (no email) <eric>
Status: RESOLVED FIXED    
Severity: Normal    
Priority: P2    
Version: 412   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
XHTML 1.0 Frameset document that uses a .xml extension
none
XHTML 1.0 Frameset document that uses a .html extension none

Chris Petersen
Reported 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 ?
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 attachment proposed patch, testcase, etc.
Chris Petersen
Comment 1 2005-06-03 21:41:34 PDT
Created attachment 2098 [details] XHTML 1.0 Frameset document that uses a .xml extension
Chris Petersen
Comment 2 2005-06-03 21:42:38 PDT
Created attachment 2099 [details] XHTML 1.0 Frameset document that uses a .html extension
Chris Petersen
Comment 3 2005-06-07 11:45:43 PDT
Apple Bug : <rdar://problem/4141211>
Daniel Udey
Comment 4 2005-11-09 10:14:44 PST
This bug is confirmed in Safari 2.0.2 but works properly in ToT.
Note You need to log in before you can comment on or make changes to this bug.