Khalid Lafi

I tried it on a dropped index, and it's working. Can you tell me the steps to reproduce it?

i haven't used it for a while. but i do plan on keeping bug free at least. So, yes please report the issue you have.

i don't think i understand what you're getting at?

Why would it produce collisions?

Sorry, it's fixed now. http://wpotools.github.io/perfBar/

I don't front-end work anymore, so i can't really find time to do it. If you're interested, i can give you commit permission, and you can take over the project....

Because there's no conditions to satisfy Look at line [#163](https://github.com/WPOTools/steady.js/blob/master/Steady.js#L163) ``` javascript if ( !self._wantedTrackers.length || self.processing ) return; ``` if there's no trackers (a.k.a conditions) Steady.js won't do anything...

I'm sorry, but i see that as an anti-pattern.

Because it's most likely that this handler will be executing different logic based on the location of the user in the page. Which means breaking down the code to each...

It's different, this issue is to build a gulp plugin for RWDPerf. So, others can integrate it in their workflow.