[Webkit-unassigned] [Bug 150271] New: float:right not working consistently across page loads (Loading-related race condition?)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Oct 16 23:35:04 PDT 2015


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

            Bug ID: 150271
           Summary: float:right not working consistently across page loads
                    (Loading-related race condition?)
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Macintosh
                OS: Mac OS X 10.10
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: CSS
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: webkit at chrisrebert.com

Created attachment 263362
  --> https://bugs.webkit.org/attachment.cgi?id=263362&action=review
Screenshot of incorrect rendering

Original downstream Bootstrap bug:
https://github.com/twbs/bootstrap/issues/17913

Steps to reproduce the problem:
1. Download the ZIP for https://gist.github.com/cvrebert/14f296e3629e177da6c2
2. Unzip it.
3. Download http://code.jquery.com/jquery-1.11.3.min.js to the unzipped folder.
4. Open example.html in WebKit Nightly.
5. While looking at Button 2, refresh the page repeatedly.

What is the expected behavior?
Button 1 and Button 2 should be vertically aligned.

What went wrong?
Sometimes Button 2 renders completely below Button 1, vertically speaking.


In the course of trying to further simplify the testcase, I seemed to observe the following:
* The <div class="hidden"></div> is necessary to manifest the bug.
  * Changing it to <div style="display:none;"></div> avoids the bug
  * Moving the code for the .hidden class (`.hidden { display: none !important; }`) out of the external CSS file and into the <style> tag in the <head> avoids the bug.
* The bug does not manifest if jQuery is removed, even though the webpage doesn't actually invoke jQuery anywhere.

Based on these observations, I speculate that the bug might be some kind of race condition related to the loading of external assets.


Analogous Chrome bug: https://code.google.com/p/chromium/issues/detail?id=544290
Firefox is NOT affected by this bug.
I don't have a Windows box available to test MS Edge.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151017/0f02cfd6/attachment.html>


More information about the webkit-unassigned mailing list