LazyLoad experimental Flag behaving differently with HTTP vs. HTTPS image requests
Reported by
doug.sil...@gmail.com,
Sep 20
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. turn on enable-lazy-load 2. load https://dougsillars.github.io/indexbg_opt.html and observe lazy loading order of images (top -> bottom. 3. load load https://dougsillars.github.io/indexbg_opt_https.html (where image requests are HTTP2). See that the order of image load is not top-> bottom What is the expected behavior? I would expect HTTP AND HTTPS requested images to Lazy Load the same way. What went wrong? with the lazy load flag on, the HTTPS image requests load in the same order as if Lazy Loading was not on. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 71.0.3557.0 Channel: canary OS Version: OS X 10.13.6 Flash Version:
,
Sep 24
Unable to reproduce the issue on mac 10.13.3 using chrome reported version #71.0.3557.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Turned on enable-lazy-load 2. Loaded https://dougsillars.github.io/indexbg_opt.html and observe lazy loading order of images are from top -> bottom. 3. Loaded https://dougsillars.github.io/indexbg_opt_https.html (where image requests are HTTP2). Observed that the order of image load is also from top-> bottom. doug.sillars@ - Could you please check the attached screen cast and please let us know if anything missed from our end. Thanks...!!
,
Oct 29
Mac triage: WontFix issue without repro steps. |
|||
►
Sign in to add a comment |
|||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 21