In my JavaScript, I have implemented an effect (hiding a title bar) triggered by a scrollEvent. So when I scroll down, the title bar is hidden, as I begin to scroll up, it is revealed. This is a familiar affect to most mobile browsers.
Here's the thing... with devtools open, it works just fine. If I close devtools, the effect no longer works, ie. the title bar remains visible as I scroll down. If I reopen devtools (ctrl-shift-j), the effect works again. I run devtools in a separate window, so its presence doesn't affect the window dimensions of my app.
Does anybody know what influence the presence of Chrome devtools has on Javascript or rendering behaviour?
NB, for any speed readers that miss the point of my question, I am not asking for a solution to the problem I'm seeing. I'm specifically only asking for answers to my question.
from How does having Chrome devtools open change behaviour?
No comments:
Post a Comment