RESOLVED INVALID 7092
Resizing is done badly, upper left corner isn't anchored.
https://bugs.webkit.org/show_bug.cgi?id=7092
Summary Resizing is done badly, upper left corner isn't anchored.
Shawn Smith
Reported 2006-02-05 15:56:07 PST
When opening the nikon website a strange painting error occurs with the safari window. Not even sure how to describe it.
Attachments
Testcase (2.94 KB, text/html)
2006-02-06 00:07 PST, Joost de Valk (AlthA)
no flags
Testcase with larger time outs (3.04 KB, text/html)
2006-02-06 00:15 PST, Joost de Valk (AlthA)
no flags
Better testcase (2.94 KB, text/html)
2006-02-06 00:17 PST, Joost de Valk (AlthA)
no flags
A test-case exaggerating the behavior. (559 bytes, text/html)
2012-01-03 14:17 PST, Tony Sung
no flags
David Kilzer (:ddkilzer)
Comment 1 2006-02-05 20:55:23 PST
Confirming bug. This is not a regression--it happens on Safari 2.0.3 (417.8) on 10.4.4 as well. I would describe the behavior as "bouncing", although the entire window contents bounces inside its boundary, not just the HTML content area. FREAKY!
Joost de Valk (AlthA)
Comment 2 2006-02-05 21:56:16 PST
I'll reduce this one... Assigning to myself :P
Joost de Valk (AlthA)
Comment 3 2006-02-06 00:07:22 PST
Created attachment 6281 [details] Testcase This testcase shows issues with how we handle setTimeout, don't know if this is a bug. This occcurs repeatedly in the code for the site: if ( ( ismc ) && ( document.all || issafari ) ) { clearTimeout(macTimeout1); clearTimeout(macTimeout2); macTimeout1 = setTimeout("window.resizeBy(1,1);",100); macTimeout2 = setTimeout("window.resizeBy(-1,-1);",200); } this causes the "shake". The testcase shows this as well and shows that we handle timing differently then Firefox.
Joost de Valk (AlthA)
Comment 4 2006-02-06 00:13:46 PST
As the reduction shows, this is not a painting issue, the scripts do multiple resizes on purpose and just for Safari. If i use User-Agent Mozilla 1.1, this does not occur and the site works fine. So these guys need to be evangelized, CC-ing Mark Malone for that. The other issue here is that the timers fire in the wrong order it seems. Renaming, attaching better testcase with larger timeouts in a sec.
Joost de Valk (AlthA)
Comment 5 2006-02-06 00:15:24 PST
Created attachment 6282 [details] Testcase with larger time outs 1000 instead of 100 and 2000 instead of 200 ms.
Joost de Valk (AlthA)
Comment 6 2006-02-06 00:17:28 PST
Created attachment 6283 [details] Better testcase Now correctly.
Joost de Valk (AlthA)
Comment 7 2006-02-06 00:24:12 PST
Ok, this bug will be on resizing the window. The upper left corner isn't anchored and resizing in general looks weird, flashy and slow and not clean like f/i Firefox. This bug will track that. Timing issues, if any, will be tracked in another bug. Reassigning back to webkit-unassigned.
Joost de Valk (AlthA)
Comment 8 2006-02-06 00:59:15 PST
The timing issues are filed in bug 7099.
Joost de Valk (AlthA)
Comment 9 2006-06-24 14:22:41 PDT
*** Bug 9285 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 10 2007-12-29 12:25:20 PST
This actually looks like a Safari issue: the calculations that WebKit performs before asking Safari to resize the window seem to be correct. Also, Safari is apparently setting window minimum size as a result of this test - manual resizing no longer works correctly.
David Kilzer (:ddkilzer)
Comment 11 2007-12-29 13:47:19 PST
Alexey Proskuryakov
Comment 12 2010-03-26 16:18:35 PDT
*** Bug 31033 has been marked as a duplicate of this bug. ***
Tony Sung
Comment 13 2012-01-03 14:15:04 PST
*** Bug 68419 has been marked as a duplicate of this bug. ***
Tony Sung
Comment 14 2012-01-03 14:17:01 PST
Created attachment 120996 [details] A test-case exaggerating the behavior. Attached another test case which exaggerate the behavior: Resize the browser window (making it smaller) using window.resizeTo() will cause window's title to be clipped. To reproduce 1. Open the attached test-case in a new browser window (not in a tab, because window.resizeTo() doesn't work in a tab). 2. The test-case will automatically resize the browser for 5 times with an interval of 1-2 seconds. 3. Observes the window's title being clipped during each resize.
Robert Hogan
Comment 15 2013-07-23 11:12:54 PDT
Is this still a valid bug? I can't recreate it at all but I'm not sure that I'm doing it right!
Ahmad Saleem
Comment 16 2023-09-20 08:13:23 PDT
@Alan - I think browsers are now evolved and we have hardware which can manage these resizing issues. Plus I am not able to reproduce this bug, can we mark this as 'RESOLVED CONFIGURATION CHANGED' or 'RESOLVED WONTFIX'?
zalan
Comment 17 2023-09-28 08:22:15 PDT
The attached test case looks performant to me.
Note You need to log in before you can comment on or make changes to this bug.