I'm using 'Chrome 39.0.2171.95 m' and 'Atlassian FishEye analysis with Crucible code review. (Version:3.5.4 Build:20140917115234 2014-09-17)' and for some reason the next and previous element buttons and keys will only bring a page down by a fraction of a line, not getting anywhere near the actual element. For very large files this can be very difficult to get to all the elements and review them properly.
This works correctly in 'Firefox 34.0.5'.
Is this a known issue?
Community moderators have prevented the ability to post new answers.
Hi Shane,
It seems to be a bug that it should fixed in Crucible 2.9.0 as you can see here:
https://jira.atlassian.com/browse/CRUC-5781
As a workaround you can try to attach a dummy file (an empty file) to the review will prevent the browser from hanging.
Hope this helps!
Cheers,
wZ
We are encountering the same problem, however we are using FishEye and Crucible 3.7.0.
The browser (Chrome) does not hang, but the next and previous element buttons and keys will only bring a page down by a fraction of a line. Additionally, the Crucible review does not only contain one file.
Is there an update?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, does not work in Chrome, but works in Firefox.
Can we please fix?
The Tampermonkey work around doesn't work for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am experiencing this in Fisheye (with Crucible) version 3.4.3, build 20140508130738 (2014-05-08).
This seems to be an issue with animations in the version of jQuery used. I was able to work around the issue by installing the Tampermonkey Chrome extension and adding the following script:
window.addEventListener("load", function () { jQuery.fx.off = true; });
This disables all jQuery animations. As a caveat, all other jQuery animations (such as highlighting the element that gets scrolled to) are disabled as well, but at least I can scroll effectively now.
The root issue seems to stem from the duration of the animation coupled with some synchronous process taking too much time on the front-end.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, according to Atlassian, this is a known issue. I don't think there is a date for resolution yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are also seeing this with FishEye and Crucible 3.7.0. Chrome version 41.0.2272.118. The review contains two files. The first forward does correctly move to the next item but that item requires no scrolling of the code window. Unified diffs and full context settings were in use.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.