Our app honors it as much as it can, but the browser does not. Many people consider it essentially a "battery saver" mode.

Most, usually all, of our data access, including extending concurrent licenses, is done by direct decision by the app, and it honors the in app setting to go to offline mode and not use the internet.

But some caching is done by the browser. In particular things like the manuals and some other files are cached by the browser.

If you put it into offline mode, your changes will not be sync'd (saved) to the server until you put it back in online and have a connection to the internet, and you will then get changes that other people made.

If you look at our document system, the app may have cached the list (tree) of documents available. If so, you can see the list (tree) of documents that were available before you went offline. But the documents themselves are cached by the browser, and the browser has its own rules for how long to cache them.

This means if your device is 'online' but you set the app to work in 'offline', if you have the tree of documents is not cached by the app, you will not see the list (tree) of documentation. But if the list of documents is cached by the app, it will show you the tree, and then when you go to a document you never have used before, the browser will go out and get it and ignore the in-app setting to be offline.

The app doesn't know what is cached by the Browser, so it ignores the in-app setting for offline and asks for the file. The browser then goes and grabs the file, from its cache if it has it, or live if there is a connection.

If you have seen a specific manual before, it is up to the browser to decide when to delete it from cache. The algorithm for this changes from browser to browser, version to version, platform to platform and the browsers don't make it 'really' public. In theory you could go and read the current version's code and figure it out with each release and on each platform, but it practice, it isn't public information.

The result is that at some point, due to factors the browser authors decide, a file you previously saw will be removed from memory.

Similarly, most images are cached by the browser, not by us.

You can force the browser to clear it's cache, but that is usually a bad idea and if you have unsync'd changes, they will be lost, and if you have any licenses, it will be a while before they are released - named licenses take up to 72 hours, concurrent take however long they were currently set to last.

The offline mode of our app will only prevent our app from going out and grabbing live. So sync's stop functioning, license checks stop running etc.., depending on your purposes, you could consider it more of a battery saving mode than a "don't get online documents" mode.

Useful for a lot of testing, but not an absolute prohibition to go to the internet.

If you really want to block internet access, do it at the OS level, put it in flight mode and turn WiFi off if it is still on for example.