RESOLVED WONTFIX 12138
Menus on peachtree.com don't display correctly
https://bugs.webkit.org/show_bug.cgi?id=12138
Summary Menus on peachtree.com don't display correctly
Victor Morel
Reported 2007-01-06 09:44:31 PST
The page has a problem with the menus. When you load the page, instantly you will view the problem in the up left corner with menu displaying.
Attachments
David Kilzer (:ddkilzer)
Comment 1 2007-01-06 11:14:32 PST
Confirmed with locally-built debug build of WebKit r18639 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8N1037).
Matt Lilek
Comment 2 2007-01-06 14:17:42 PST
Identifying as Mozilla causes the site to work fine. However, there are some visual glitches with the menus displaying under the flash (using Flash Plugin 9.0 r28 on a debug build of r18638) though I'm not sure whether thats already a known issue.
reeves_28
Comment 3 2008-10-24 11:14:01 PDT
This pages works if you set the User Agent to match a browser other than Safari.
Sam Sneddon [:gsnedders]
Comment 4 2009-04-21 11:02:45 PDT
The bug here is in the script: it explicitly sniffs for Safari, and if it is Safari, gives it broken content. Safari's rendering of the content it gets is consistent with Firefox.
Ahmad Saleem
Comment 5 2023-05-07 00:23:44 PDT
(In reply to Sam Sneddon [:gsnedders] from comment #4) > The bug here is in the script: it explicitly sniffs for Safari, and if it is > Safari, gives it broken content. Safari's rendering of the content it gets > is consistent with Firefox. Considering it was website sniffing script issue in the past, similarly when I retrieve this webpage from Wayback archive (just a day before user reported): https://web.archive.org/web/20070105053313/http://www.peachtree.com/ ^ I am unable to reproduce this bug of menu issues and also this site required 'Flash', which I can compensate using 'Ruffle' on Chrome (but not on Safari). Wayback Archive copy is loading this website similar (in drop-down menu as well) in all browsers (STP169, Chrome Canary 115 & Firefox Nightly 114). Marking this as "RESOLVED WONTFIX" (since it was site issue).
Note You need to log in before you can comment on or make changes to this bug.