Bug #1274
openImages triggered on after tabs refresh on memory reload
Added by ask low 9 days ago. Updated 9 days ago.
0%
Updated by Soren Stoutner 9 days ago
- Priority changed from 3.x to Next Release
Thanks for the bug report. I will take a look at it when I get the chance.
Updated by Soren Stoutner 9 days ago
Are images disabled app-wide or with Domain Settings?
Updated by Soren Stoutner 9 days ago
I don't imagine a log would be very helpful in this case. Usually it only contains useful information if there is a crash.
Can you clarify what method you have used to disable images for the tab before the app is restarted?
Updated by Soren Stoutner 9 days ago
So, to make sure I understand, you have displaying images disabled app-wide. When the app restarted, one of the tabs displayed images and the others didn't?
Updated by ask low 9 days ago ยท Edited
It is all the opened tabs tbh. You can reproduce this yourself.
1. Keep Images off from preferences.
2. Open any image heavy websites (single or multiple doesn't matter) without Images.
3. Make sure you don't enable Images from any of their page menus.
4. Trigger memory refresh by your android's app switcher.
5. Come back to the opened page.
It should have it's images turned itself on after the page reload.
Updated by Soren Stoutner 9 days ago
I am able to replicate the behavior. I'll have to see if there is anything I can do about it. It looks like Android's WebView is not preserving the display image status as part of the WebView settings (probably because they don't think it is important). There might be a way I can manually save and restore the state, but that should already be happening with the app-wide settings, so it is also possible that WebView ignores this setting and uses its own internal default when restoring states.