4 ms·
Very interesting. I'll have to try it out. The first thing I'll look at is how it deals with the jQuery changes being visible to the visitors (aka flicker/flash
by karolisd 14y ago
Very interesting. I'll have to try it out. The first thing I'll look at is how it deals with the jQuery changes being visible to the visitors (aka flicker/flashing). Do you hide the page and wait for document to be ready?
Do you do continuous checking of the DOM like Optimizely? Diagram: http://support.optimizely.com/customer/portal/articles/452881-how-when-does-optimizely-evaluate-my-variation-javascript-code- http://support.optimizely.com/customer/portal/articles/45288...
- maccman 14y agoThe trick is to place your a/b testing JavaScript right after the relevant DOM elements, and not do a/b testing on DOMReady or window.load. That'll ensure there's no flickering.
- karolisd 14y agoI'm just hoping someone comes up with perfect way I can just put a script in the head and not worry about flickering. So I don't have to hide the body with CSS and make it visible when the script finishes. Optimizely seems to be getting there, but it's not perfect. (And kind of awkward, why can't browsers provide a better way to target elements as they come into existence?)
- sandstrom 14y agoI agree, we use CSP and hence no inline scripts.a method to avoid flicker would be great!