RESOLVED WONTFIX 40777
cPanel 
https://bugs.webkit.org/show_bug.cgi?id=40777
Summary cPanel
oliver
Reported 2010-06-17 07:14:07 PDT
cPanel is a main interface for a lot of hosting companies. Safari has had continual bugs with the cPanel that was released a few months ago. Many javascript errors (like when trying to change MX records). With Safari 5, now the entire cPanel is messed up. none of the icons even show up and clicking on certain buttons gives page errors. Too many bugs to list. just go ahead and use Safari with any cPanel and you will see. The strange thing is, Google Chrome works fine in every instance. I don't understand this because both browsers are based on Webkit. What makes it even stranger is that the nightly builds of Webkit still have all these bugs. Is Google somehow fixing these bugs for their browser, but not letting the Webkit developers know about them?
Attachments
screenshot (154.62 KB, image/png)
2010-06-17 07:16 PDT, oliver 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
oliver
Comment 1 2010-06-17 07:16:15 PDT
Created attachment 58992 [details] screenshot screenshot of cPanel with missing images.
Alexey Proskuryakov
Comment 2 2010-06-17 14:23:21 PDT
> just go ahead and use Safari with any cPanel and you will see Do you have an example URL where I could try it? > What makes it even stranger is that the nightly builds of Webkit still have all these bugs. From your description, it sounds like cPanel performs browser detection and serves different content to Safari. You can verify this by enabling Developer menu (via Safari advanced preferences), and forcing user agent to Firefox, then reloading a page. If that fixes the problems, then my idea is correct, and we're just getting a broken version of the site.
Ahmad Saleem
Comment 3 2022-09-12 15:17:31 PDT
Lack of reproducible test case or hints on why this is Safari / Webkit bug or it was temporary issues. Since we don't have any clear indications on how to fix this issue, I am going to mark this as "RESOLVED WONTFIX". Please reopen, if you think it is reproducible with test case. Thanks!
Note You need to log in before you can comment on or make changes to this bug.