Closed Bug 1149206 Opened 10 years ago Closed 9 years ago

Fetch raw reading list content in Java, not only in Gecko

Categories

(Firefox for Android Graveyard :: Reading List, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rnewman, Unassigned)

References

Details

(Keywords: meta)

As I understand it, we just use a simple XHR to grab content. We don't actually evaluate the page at all. That implies that we can have a 'rawcache' -- a new item that arrives in the background when Gecko isn't running can be snarfed down via ordinary Java code. The existing readerizing code can then first try to load from the rawcache instead of from the web, which means we can have your reading list ready for you when you launch the browser, even if you're offline.
(In reply to Richard Newman [:rnewman] from comment #0) > As I understand it, we just use a simple XHR to grab content. We don't > actually evaluate the page at all. Well, we do reader-ize the result of that XHR and then store the article object in the cache. But I think you just mean we never load that HTML response in a browser. > That implies that we can have a 'rawcache' -- a new item that arrives in the > background when Gecko isn't running can be snarfed down via ordinary Java > code. The existing readerizing code can then first try to load from the > rawcache instead of from the web, which means we can have your reading list > ready for you when you launch the browser, even if you're offline. Yeah, this sounds like a good idea. We can have a code path to reader parse that raw cache content, and then fall back to loading the original URL if that fails.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.