"Work Offline" feature in developer tools settings
2,651 views
Skip to first unread message
stefanki...@gmail.com
unread,
Feb 6, 2013, 7:26:14 AM2/6/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-chrome-...@googlegroups.com
To test e.g. HTML5 application cache it woulb be nice to switch chrome in offline mode (like Firefox).
New checkbox in developer tools settings would be great.
Addy Osmani
unread,
Feb 8, 2013, 6:50:21 AM2/8/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-chrome-...@googlegroups.com, stefanki...@gmail.com
There has been a lot of work done recently to implement an offline mode in Chrome itself. See https://code.google.com/p/chromium/issues/detail?id=2204/. The best thing that DevTools could do here is expose a convenient toggle for online/offline but the implementation itself is best left up to the browser. Hopefully this is something that will land in the not too distant future :)
Addy Osmani
unread,
Feb 8, 2013, 6:58:40 AM2/8/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-chrome-...@googlegroups.com, stefanki...@gmail.com
Actually, that issue seems to be mostly about using stale cache entries if we can't get anything fresh due to network issues. We think it would still have to be done in the browser's network stack, but there's a chance it would be rather simple. From the DevTools side it would still mostly be hooking up plumbing to what the browser already provides.