RESOLVED CONFIGURATION CHANGED 4052
Worldbank tables do not display correctly, losing information.
https://bugs.webkit.org/show_bug.cgi?id=4052
Summary Worldbank tables do not display correctly, losing information.
Scott Ellsworth
Reported 2005-07-18 12:43:22 PDT
The world bank uses front page to create their data tables, and something in the HTML causes the top of the tables to be trimmed. Note in the above URL that the first country listed is Angola. Algeria is trimmed, and Albania is missing entirely. In addition, the right column of the page is not laid out in a way that can be seen. A web archive of the page is available at <http://homepage.mac.com/fuz/Table%204.15%20|%20Balance% 20of%20payments%20current%20account.webarchive>, in case the world bank removes the original.
Attachments
webarchive of misbehaving page (373.15 KB, application/x-webarchive)
2005-07-18 12:44 PDT, Scott Ellsworth
no flags
Scott Ellsworth
Comment 1 2005-07-18 12:44:05 PDT
Created attachment 2996 [details] webarchive of misbehaving page
David Storey
Comment 2 2005-07-19 14:47:07 PDT
Confirmed in 10.3.9. Frontpage produces very poor html so that'll be the problem. doesn't work in Gecko either. I'm quite impress that Opera gets it right though.
Joost de Valk (AlthA)
Comment 3 2005-12-29 06:48:23 PST
Confirmed that rendering is wrong, but I'd have to say this is a wontfix, i've tried reducing it but the html is so incredibly bad that there is no use. Firefox doesn't get it right either so i don't feel tempted to do this... anyone else? Reassigning to webkit-unassigned.
Scott Ellsworth
Comment 4 2006-01-03 11:59:35 PST
If nothing else, it would be worth trying to come up with some statement of what is wrong, and sending it to them. Perhaps they can be coerced into changing their HTML if given a decent list of why it bites. Scott
Alexey Proskuryakov
Comment 5 2007-01-06 15:24:31 PST
The site has changed a lot, and I couldn't find any table like this on it anymore. The attached webarchive is rendered the same way in WebKit and Firefox, so I suggest closing this bug.
Brent Fulgham
Comment 6 2022-07-06 11:36:12 PDT
Safari, Chrome, and Firefox all have the same behavior on the attached webarchive, so I believe the compatibility issues have been resolved.
Note You need to log in before you can comment on or make changes to this bug.