Description
The extension currently depends on four page-context globals that geocaching.com could remove in any modernization push: the page's jQuery, $.tmpl + the tmplCacheLogRow template, userToken, and $.fn.fancybox. The site has been drifting toward React; any one of these disappearing kills the extension completely (and is the likely mechanism behind #85).
Proposed Fix
- Fetch
/seek/geocache.logbook directly from the content script (session cookies are already sent) instead of via injected page-context code - userToken extraction from page HTML remains the only page dependency
- Render log rows with the extension's own template/DOM code instead of
$.tmpl
- Drops three of four fragile dependencies and makes the remaining one (userToken) trivially assertable by the canary
Description
The extension currently depends on four page-context globals that geocaching.com could remove in any modernization push: the page's jQuery,
$.tmpl+ thetmplCacheLogRowtemplate,userToken, and$.fn.fancybox. The site has been drifting toward React; any one of these disappearing kills the extension completely (and is the likely mechanism behind #85).Proposed Fix
/seek/geocache.logbookdirectly from the content script (session cookies are already sent) instead of via injected page-context code -userTokenextraction from page HTML remains the only page dependency$.tmpl