In AE CC 2015 v13.5 on OS X 10.11, when caps lock is activated, scrubbing the timeline with the mouse stops frames from being calculated, as expected. However, when I use cmd+arrow keys or cmd+shift+arrow keys to navigate the timeline with caps lock activated, frames are still calculated.
In addition to that, while a frame is being calculated, AE completely ignores all keyboard input until the frame is finished calculating.
This is a huge problem, because keyboard navigation allows me to quickly step forward or backward by a specific number of frames. In CC 2014, even without caps lock activated, I could continue to navigate the timeline without waiting for every single frame to be calculated. This is a slowdown of a very basic function.
Using the mouse for a similarly precise navigation of the timeline requires counting frames manually, and is a huge slowdown as well, even though caps lock seems to do its job when using the mouse. Not to mention the added slowdown of having to constantly switch between keyboard and mouse simply to navigate the timeline.
This wasn't an issue in CC 2014 and I'm considering rolling back to that installation, because this is one of myriad problems that CC 2015 has introduced.