Bug 41860

Summary: Frameset cols and rows values reported and set incorrectly
Product: WebKit Reporter: Tim Green <tim.green>
Component: FramesAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: christopher.reiss, dbates, tim.green
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://www.ignitebyte.net/info/webkitbug/
Attachments:
Description Flags
Test Case
none
Test Case
none
Test Case Archive none

Tim Green
Reported 2010-07-08 08:32:27 PDT
Related to: https://bugs.webkit.org/show_bug.cgi?id=36584 Current Webkit browsers (Safari and Chrome in OS X and Windows are all affected) fail to read and write frameset dimensions correctly via JavaScript if the user has changed the frame dimensions by dragging the frame border with the mouse. Reading the cols value returns the original static setting from the frameset page. Writing the cols value ADDs the change by the user to the entered value as a positive or negative offset, producing garbage results. For example, if the user has moved the frame border to the right by 50 pixels, setting cols to "0%,100%" will result in a left frame with a width of 50 pixels. If the user has moved the frame border to the left setting "0%,100%" will produce a left frame with a width of -50 pixels. In both case reading cols will still return the original static value from the page. This makes workarounds impossible, thus it looks critical. For example, it breaks webhelp systems that load a table of contents and related topics into left and right frames, emulating the behavior of help systems like MS HTML Help CHM files.
Attachments
Test Case (41 bytes, text/plain)
2010-07-08 08:37 PDT, Tim Green 		no flags
Details
Test Case (325 bytes, text/html)
2010-07-25 20:30 PDT, Daniel Bates 		no flags
Details
Test Case Archive (3.21 KB, application/zip)
2010-07-25 20:42 PDT, Daniel Bates 		no flags
Details
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Tim Green
Comment 1 2010-07-08 08:37:32 PDT
Created attachment 60888 [details] Test Case Demonstrates the issue and its consequences
Daniel Bates
Comment 2 2010-07-25 20:30:50 PDT
Created attachment 62537 [details] Test Case Attaching test case from <http://www.ignitebyte.net/info/webkitbug/> for historical preservation.
Daniel Bates
Comment 3 2010-07-25 20:42:44 PDT
Created attachment 62539 [details] Test Case Archive
chris reiss
Comment 4 2011-04-13 07:16:25 PDT
looking into this ...
chris reiss
Comment 5 2011-04-19 07:41:08 PDT
Is this something WebKit cares to fix, since framesets have been deprecated ?
Daniel Bates
Comment 6 2011-04-26 13:09:48 PDT
Lowering priority and importance since this doesn't sound like a crash or a regression.
Note You need to log in before you can comment on or make changes to this bug.