[Webkit-unassigned] [Bug 52110] New: images get rendered incorrectly in first attempt, second attempt may be ok

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=52110

           Summary: images get rendered incorrectly in first attempt,
                    second attempt may be ok
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
               URL: http://wk.ac52.de
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Images
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mh at dsgn.ac52.de


The images I referre to should appear in the down-left corner of the box.

The bug was observed form different plattforms and different browsers: WinXP with Chrome 8, Linux Debian/Sid with Arora +Webkit 532.4, Midori + WebkitGTK+ 1.2.3 Debian/Squeeze (Qt-webkit 4.6.3 (libqt4-webkit)), Ubuntu 10.04 (Qt-webkit 4.6.2) sowie Fedora 14 (Qt-webkit 4.7.1). It is related only to webkit based browsers, absolutely no problem with other browsers like Opera 11, FF, IE 6/7/8.

Google Instand View (little preview box which you may activate in the Google SERPs) shows the same rendering bug with a website I created. I will provide this URL in private only. So if you like to see this you need to provide an emailaddress where I may sent the respective URL to. 
The example I am posting here is the same sourcecode with commented out as much elements as possible. It is hosted on the same server but on an other domain and probably not indexed yet. So you will not be able to see the Google rendering bug with this example here.

Further: I (and others) could not reproduce this bug localy, it only occurs when the website comes from the server. OTAH, I compared the sourcecode when the bug is triggerd and there is absolute no difference. So I think the server can be excluded as source of the bug.

Now if the bug occurs, you may "heal" it by adding "www." in front of the URL or "/index.html" at the end (but you may as well begin with the "long" URL and the cut off the unnecessary "index.html"). Sometimes it may be sufficient to simply reload the website. And depending on the cirumstances, you may trigger this bug only once. 
- The bigger the sourcecode is and the longer the local machine runs (RAM fragmentation or whatever) the more likely it is you may not heal the bug by reloding the page and the more often you may reproduce the bug. 
- The more the soucecode is reduced and with a fresh booted machine you my reproduce the bug only once.

This is not limited to my computer as you may see in the Google SERPs. 

My personal conclusion is that there is some timing issue which leads to the bug.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.