Small bug with images partially visible

[jdeniau]

I have a small bug detected in responsive case. Here is the example:

a 1400x400px banner, centered on the browser.

On mobile (let's say width = 500px), the top-left pixel position is top: 0, left: (500 - 1400)/2 = -450px As 450 > the base offset, the image is considered as not inViewport, but as the image width is 1400, it should be considered "in".

Thank you

[vvo]

@jdeniau For an easy bug resolution of this use case, please provide a working example of the https://github.com/vvo/in-viewport library given your test case.

It should be pretty easy to setup and have a simple console.log() showing true/false.

Can you do that?

[jdeniau]

It will be easier that way ;)

Here is an example.

[jdeniau]

:thumbsup:

[vvo]

> bower info lazyload
bower lazyload#*                cached git://github.com/vvo/lazyload.git#2.1.0
bower lazyload#*              validate 2.1.0 against git://github.com/vvo/lazyload.git#*
bower lazyload#*                   new version for git://github.com/vvo/lazyload.git#*
bower lazyload#*               resolve git://github.com/vvo/lazyload.git#*
bower lazyload#*              download https://github.com/vvo/lazyload/archive/2.1.1.tar.gz
bower lazyload#*               extract archive.tar.gz
bower lazyload#*              resolved git://github.com/vvo/lazyload.git#2.1.1

{
  name: 'lazyload',
  description: 'Image lazy loading',
  version: '2.1.1',
  main: 'lazyload.js',
  ignore: [
    '**/.*',
    'node_modules/',
    'bower_components/',
    'test/'
  ],
  dependencies: {
    'in-viewport': '~0.4.0'
  },
  homepage: 'https://github.com/vvo/lazyload'
}

Available versions:
  - 2.1.1

[vvo]

@jdeniau Can you test for yourself if it works?

[jdeniau]

I'll test it next week Le 6 juin 2014 15:14, "Vincent Voyer" notifications@github.com a écrit :

@jdeniau https://github.com/jdeniau Can you test for yourself if it works?

— Reply to this email directly or view it on GitHub https://github.com/vvo/lazyload/issues/56#issuecomment-45334884.

[jdeniau]

Oops, I took time to test it but the bug is fixed ;)

Thank you