Ameer Jhan

@inductor this is a valid point, will add this for the next release

No im still open for it

@ucarbehlul I'm unable to understand the problem, can you please elaborate

@pulpiks I think this is a duplicate PR for #213

@frankn11 we fixed this in the lates version, also please try the beta version which also has a potential fix

@frankn11 can you provide a codesandbox link which replicates your issue

Hi @simplecommerce this span is necessary to avoid usage of findDom API and ReactRef actually needs a dom element in the jsx, the className in the span tag is provided...

@simplecommerce the findDom was deprecated and it was causing warning in lot of productions that is why we switched to React Ref. I can understand your concern that the consumers...

@simplecommerce for your reference https://github.com/twobin/react-lazyload/issues/303 we ran a beta and then switched to stable but I honestly did not anticipate this

@danielpquinn I'm also starting think on the same line, if more people are affected I will make this into a Major update