Bug description
When a has an effect property defined (e.g. "opacity"), the image is wrapped with a span (where all the corresponding classes are applied (e.g. lazy-load-image-loaded)). Said span comes with some styles already defined in the component, as seen in method getWrappedLazyLoadImage() of LazyLoadImage.jsx. This raises problems when the wrapping element is expected to have its default behavior. In my case, I needed it to stay displayed as a block (as an
would be), but instead it becomes an inline-block. In my case it breaks my view (see screenshot below)
To Reproduce
Create a with an effect and inspect it.
<LazyLoadImage src="test.jpg" alt="Test" effect="opacity" />
Expected behavior
The wrapping element shouldn't change how the component is rendered.
Perhaps the style for the wrapper should be defined in the CSS of each effect instead.
Screenshots

Technical details:
- Package version: 1.3.2
- Server Side Rendering? No
- Device: any
- Operating System: doesn't apply
- Browser: happens with both Firefox and Chrome
Maybe it is related -or can be circumvented- if #31 is implemented
Bug description
would be), but instead it becomes an
When a has an
effectproperty defined (e.g."opacity"), the image is wrapped with a span (where all the corresponding classes are applied (e.g.lazy-load-image-loaded)). Said span comes with some styles already defined in the component, as seen in methodgetWrappedLazyLoadImage()of LazyLoadImage.jsx. This raises problems when the wrapping element is expected to have its default behavior. In my case, I needed it to stay displayed as ablock(as aninline-block. In my case it breaks my view (see screenshot below)To Reproduce
Create a with an effect and inspect it.
Expected behavior
The wrapping element shouldn't change how the component is rendered.
Perhaps the style for the wrapper should be defined in the CSS of each effect instead.
Screenshots

Technical details:
Maybe it is related -or can be circumvented- if #31 is implemented