zotero/chrome
Dan Stillman 4d94810def Don't send a conditional request for an invalidated retractions cache
The cached retractions list is saved with the current data version from
the code, which we can bump to make clients discard their cached data
and refetch it. We've never actually done that, but if we did, it
would've hit a bug: init() would've started the refetch but still sent
the cached ETag, so if the list itself hadn't changed, the server
would've returned 304 and nothing would have been updated. The stale
version then would have survived, so the refetch would have been retried
on every startup.
2026-09-04 13:27:12 -04:00
..
content Don't send a conditional request for an invalidated retractions cache 2026-09-04 13:27:12 -04:00
locale Show file access error for NS_ERROR_FILE_FS_CORRUPTED 2026-09-04 12:37:49 -04:00
skin/default/zotero Center single-paragraph items pane status messages when they wrap 2026-09-02 22:16:13 -04:00