Back in May, GitHub rolled out changes to the code search and code view.
The changes code search were necessary to address infrastructure issues. There are some features missing from the new code search.
The code view changes attempt to, and fail to, reimplement standard browser behavior while displaying code in a heavily customized textarea element. This breaks keyboard shortcuts for the back button and other standard browser behaviors. There is no option to opt out of the UI changes.
GitHub appears to be accepting bug reports in the linked discussion but managing them on an internal tracker. It is unclear why they are not using the same issue tracker they provide to their customers.
Personally, I find the changes persistently annoying. In the linked discussion thread, developers are a bit more ruthless with their feedback.
2 comments
[ 2.2 ms ] story [ 13.9 ms ] threadThe changes code search were necessary to address infrastructure issues. There are some features missing from the new code search.
The code view changes attempt to, and fail to, reimplement standard browser behavior while displaying code in a heavily customized textarea element. This breaks keyboard shortcuts for the back button and other standard browser behaviors. There is no option to opt out of the UI changes.
GitHub appears to be accepting bug reports in the linked discussion but managing them on an internal tracker. It is unclear why they are not using the same issue tracker they provide to their customers.
Personally, I find the changes persistently annoying. In the linked discussion thread, developers are a bit more ruthless with their feedback.