Do not reset newly created scroller; reset height on destroy

[netzkind]

• do not reset a newly created scroller, thus saving ressources and speeding creation up
• set 'height'='' to $el on destroy - this is far from perfect, but it works for any site not setting the height to this element inline; without this, height will be stuck on destroy, so the pages rendering is not returned to normal

[kristerkari]

Is there a problem with the performance when creating the scroller? Just trying to figure out if this change is necessary.

[kristerkari]

@netzkind ping

[netzkind]

Sorry, i didn't think you are serious about this.
The reset-method in nanoscroller does loads of things, none of which is necessary to do twice to a newly created element. If there is no need to do something, then why do it?

So yes, it's a performance-problem, especially when used on low-end-devices.

[kristerkari]

@netzkind Thanks for the explanation.

I'll need to test this out on different browsers before I can pull it in. Of course if you have time or interest to help with that, then merging these changes will be easier.