-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caching with Chrome Extension #31
Comments
I would love to implement some kind of full-page cache to increase performance! I played around with the idea of making the startpage a native chrome extension back when I was first writing it, but gave up on that pretty quickly. Anyway, perhaps this could be implemented with web storage? I already use localStorage to save settings; I'll look into stashing away the whole page. It would be implemented in the next iteration of this startpage, taab, as I no longer use this older version. |
@ntomallen I've had a change of heart and would like to amend my previous statement. I will be rolling out taab as an updated to tab rather than separately because that's dumb and I don't know what I was thinking. Check out the taab branch of this repo for progress! I tried using meta tags to override HTTP headers for caching but it didn't work, might not be possible with github pages. Let me know if you have any ideas! |
Hm, I'm not sure. I actually ended up switching back to the default because I like having tab completion in the search bar. Sorry!
…On May 19, 2018, 12:47 AM -0400, Kory Schneider ***@***.***>, wrote:
@ntomallen I've had a change of heart and would like to amend my previous statement. I will be rolling out taab as an updated to tab rather than separately because that's dumb and I don't know what I was thinking.
I tried using meta tags to override HTTP headers for caching but it didn't work, might not be possible with github pages. Let me know if you have any ideas!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hey no worries, I wrote the page for my own convenience. Thanks for trying it out! |
I really love this idea. I know that the reason it can't be a local chrome extension is that Chrome forces the search/url bar to have focus the whole time. I cloned the repo and messed around with faking input commands to try to get the focus to change, but nothing worked!
Reason I started looking into that is that Chrome doesn't appear to be caching the page for the new tab. So getting to the page takes about 1.5 seconds and my internet is about 200mbs down. I was thinking implementing a service worker could serve to cache the site pages, since none of it is really dynamically updated.
The text was updated successfully, but these errors were encountered: