Bug #320
closed"Enable JavaScript by default" setting reverted when scrolled out of view
0%
Description
Nice project. I appreciate the emphasis on privacy and Tor integration.
I've attached a 17 second screencast demonstration compressed with xz (uncompressed size is slightly greater than 5Mb).
I've tried this on two different Android smartphones: 4.4.2 and 7.1.1.
As can be seen at beginning of screencast, device running Android 4.4.2 is affected but I am unable to reproduce on 7.1.1.
Might be an Android bug, and since the Android version is quite old, I don't expect a fix but nevertheless I thought you might be curious.
Good luck and take care.
Files
Updated by Soren Stoutner over 5 years ago
- Assignee set to Soren Stoutner
That is interesting. I have noticed the same behavior when testing in an emulator, but I always assumed it was a bug with the emulator. I don't have a physical Android 4.4 device to test with.
It likely has something to do with the settings being populated by an XML file, which is a newer way to do it, not being fully backwards compatible with Android 4.4. I'll poke around a little bit and see if there is some way to mitigate the problem.
Updated by Soren Stoutner over 5 years ago
- Priority changed from 2 to Next Release
Updated by Soren Stoutner over 5 years ago
- Priority changed from Next Release to 2
There appear to be a large number of spurious inputs in the settings activity on API 19, but it isn't clear to me why this is happening. Any time there is any interaction, like scrolling, all types of settings are changed, including those that are not on the screen. I can find no documentation as to why this is happening. My guess is that it is some bug in the support library.
I am going to leave this open for a while to see if I can find any way of fixing it. Ultimately, I think enough problems are going to stack up that I am going to have to drop support for API 19.
Updated by Soren Stoutner over 3 years ago
- Status changed from New to Closed
I am gong to close this bug report as there doesn't appear to be anything I can do about API 19. At this state, API 19 is handled on a best effort basis, where reasonable effort is put forth to make it work, but things that are broken are not considered to be bugs.