Description of problem: When using Ctrl+enter to move to next entry under Chrome,it will not work unless the page is refreshed. Version-Release number of selected component (if applicable): 1.6.0-beta-2-SNAPSHOT How reproducible: always Steps to Reproduce: step 1: visit a document using Chrome step 2: try to move down by hitting Ctrl+enter(won't work here) step 3: refresh page step 4: hit Ctrl+enter again(now it would work like charm!!!!) Actual results: progressed as steps mentioned Expected results: progressed as steps mentioned Additional info: firefox works properly
This appears to be a caching issue, exacerbated by the frequent deployments to our test machines. Refreshing the page appears to solve the problem until the next deployment. I should have a servlet filter to fix the cache headers soon, but it won't be happening until after 1.6. In the meantime, F5 is the workaround.
https://github.com/zanata/zanata/commit/3edf1acc777962a00357527fab59bf78dc2953dc
VERIFY with Zanata version 1.6.1-SNAPSHOT (20120620-0001) Tested with Firefox 10.0.5 Google Chrome 15.0.874.121
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause Zanata's GWT resources had no cache headers, which meant that browsers could choose to cache items which should not be cached Consequence Random editor problems (mainly on testing machines which redeploy more often than production) Fix Cacheable and non-cacheable GWT resources now have the cache headers recommended in the GWT documentation. Result Once the resources with the correct cache header have been loaded by the browser, it should avoid the random editor problems in future. Users will still need to force a browser refresh (or clear cache) if they have old data cached with the old headers.