Contributions
no colored diffs in windows dark mode
I use windows 10 in high contrast dark mode. I use chrome for code collaborator version 13.0.13002. I use the "high contrast" add-on to get chrome to reverse the colors of its content, resulting in most page being white text on a black background. So in code collaborator, I would see the highlighted differences in the files in reverse colors. Which was perfectly fine. But chrome has made some change recently where it is natively aware of windows dark mode and I no longer need the "high contrast" add-on. Chrome reverses the colors -- except *not* in code collaborator. Instead, it just reverses the text (shows white on black) for everything and somehow loses the colored difference highlighting. Reviewing code has become a horrible scan along the line numbers to find the changes the developer has made. I have tried using settings -> display -> select webUI theme -> dark to no effect. I tried classic too. I have similar issue in firefox and edge -- no colors in the file diff view. I also tried telling chrome not to go into dark mode ("--disable-features=DarkMode") but that doesn't seem to have any effect on chrome at all. Same with a couple of dark-related settings in chrome://flags/ to no or ill effect. Aside from abandoning windows dark mode (which is not a reasonable solution given my degraded eyesight), is there anything I can do to get the colored difference highlighting back in code collaborator under any windows browser?666Views0likes1CommentRe: Change Line Number that a Comment Refers To
I want to emphasize how impossible it can be to do a review when there are a lot of defects (say 10-15 or more) across multiple uploads (basically any more than 1) because of this issue of losing track of line numbers. It gets hard for the reviewer to verify that a defect is fixed (I can't find the code change), and it gets hard for a developer to figure out what code a defect is referring to (I can't find the bad code). The failure to display the code line happens even when I am looking at the upload version against which the defect was logged (that is, I picked to compare latest upload vs the upload where I logged the defect). This happens even when a file has had only 2 uploads (so there is the baseline version, the first upload against which the defects were logged, and the second/latest upload. The first re-review has defects re-ordering in weird ways depending on which version I am comparing. I am even stuck not being able to add a comment for a defect; when I type, it jumps to some other defect. The only workaround I have found is to abandon the code review and start over with a new review, where hopefully the defects logged in the original review have been mostly addressed. Which is a lot of work on the reviewer to re-review the files undergoing a lot of defects. This is turning into an almost daily battle for me, to get through increasingly difficult re-reviews. I can't believe this is being treated as an enhancement and not a bug.1.6KViews0likes0Comments