Chrome 60 showing symptom, notice white space:

https://screencast.com/t/3T4gDe8bb

Chrome 59 on the same website not showing the symptom, notice image in lower left with text "Buy More Save More"

https://screencast.com/t/0pgzrUbiiVJ

Thanks for the bug report, I can reproduce the same loading failure
on Linux M60 as well, so this may happen on any platform.

Could you make minimized test case, if any, or keep the snapshot of
failing version somewhere?

jason@ - Thanks for the issue

Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac 10.12.6 using chrome stable version #60.0.3112.90 and latest canary #62.0.3179.0.

Bisect Information:
=====================
Good build: 60.0.3078.0 Revision(466494)
Bad Build : 60.0.3079.0	Revision(466571)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/32d9f5075ba7f767d2c6c6d41794dc70b5ff7bf3..fe767186a3dc40ea14b5f807ff5438bd78f79c95

From the above change log suspecting below change
Review URL: https://codereview.chromium.org/2593263003

robhogan@ - Could you please check whether this is issue is related to your change, if not please help us in assigning it to the right owner.

Thanks...!!

Note: cc'ing manoranjanr@ and bustmante@ for review and if this can be considered as stable blocker if we plan any refresh.

Setting as Blink>Layout as the bisect points at an issue from that component.

dtapu...@chromium.org : Thank you for investigating! Please note: because it affects only a single image on our web page, we suspect there is something corrupted with that image. If so, we can likely repair our home page ourselves of course. 

Nonetheless, the fact that Chrome 60 now behaves differently than Chrome 59 (in whatever to-be-determined way it does) does indicate there was some kind of regression in Chrome. 

However, given that it is likely specific to a particular image, it would be reasonable to consider this a NO-FIX if indeed the problem can be fixed by web developers (that's your call, of course).

Nonetheless, I wanted to report it so there's a record. When/if I do identify the problem, I will *also* create a Stack overflow post to illuminate the issue for the developer community. 

We will debug our page to see if we can figure out why only this single image is the problem. Will post update here if we figure it out.

Hi Jason - when I load the page with devtools open it looks to me like Buy_more_486_optimized-min.jpg is not being requested, it doesn't show up in the network log for example. Requests for the other resources do appear, e.g. Love_it*.jpg. 

Would you be able to troubleshoot the lazyload a bit further and see why it ends up not happening?

Deleted: Screenshot from 2017-08-10 20-27-13.png 620 KB

	Screenshot from 2017-08-10 20-27-13.png 620 KB View Download

I narrowed this down to improperly specified image tags via our lazy loader.


SUMMARY OF ROOT CAUSE:
We are using jquery Lazy load version 1.9.3, which can be seen here
https://github.com/tuupola/jquery_lazyload/blob/1.9.3/jquery.lazyload.js

The issue was incorrectly formatted img tags, they contain src attributes of empty string, like such:

<img  class="lazy" src="" data-original="example.jpg" alt="">
(notice src is set to empty string)

The correctly formatted tags are without an src attribute, as the image's source is managed (first via a placeholder with a delayed load of the image):

<img  class="lazy"  data-original="example.jpg" alt="">


EXPLANATION OF ISSUE RELATED TO jQUERY LAZY LOAD

As you can see here in the code: https://github.com/tuupola/jquery_lazyload/blob/1.9.3/jquery.lazyload.js#L92

The intention of the code as per the placeholder functionality (shown here) is for there to be no src arrtibtue, e.g., to be equal to undefined or false. 

The actual line of code that cuases the problem is not 92, however, it is later here:

https://github.com/tuupola/jquery_lazyload/blob/1.9.3/jquery.lazyload.js#L99

in Chrome 59, the improperly formatted tags (with src="") triggered an 'appear' event

In Chrome 60, they do not trigger an 'appear' event, so the callback attached to line 99 does not run.

The root cause of this issue was improperly formatted html in conjuction with a specialized tool. 

Therefore I recommend no-fix/no-action to the Chromium team. I will leave this document for other developers' refernece and notify the author of jQuery Lazy Load. 

Thanks!

Deleted: 2017-08-10_1932.png 187 KB

	2017-08-10_1932.png 187 KB View Download

Thanks for getting back to us!