5 ms·
I've actually experienced this exact thing. Usually a refresh fixes it for me so I never gave it too much thought. I'm not sure what causes it exactly but I'll
by Perihelion 9y ago
I've actually experienced this exact thing. Usually a refresh fixes it for me so I never gave it too much thought. I'm not sure what causes it exactly but I'll follow up with the team about it. It usually happens to me on merge requests -- do you notice it on specific pages at all?
- sytse 9y agoI think this is due to Rails Turbolinks. Since we're deprecating Turbolinks https://about.gitlab.com/2017/02/06/vue-big-plan/ https://about.gitlab.com/2017/02/06/vue-big-plan/ I think this problem should go away.
- sytse 9y agoIt seems to be caused by and fixed in https://gitlab.com/gitlab-org/gitlab-ce/issues/28909 https://gitlab.com/gitlab-org/gitlab-ce/issues/28909
- jcrben 9y ago> Usually a refresh fixes it for me so I never gave it too much thought. As someone who hacks on a SaaS with a sprawling feature set which ships often, I understand where you're coming from. But I would recommend giving things like that some thought.