Bug #219
open
Bookmarks context action menu doesn't work right in German
Added by Soren Stoutner over 6 years ago.
Updated 11 months ago.
Description
In German, the bookmarks context action menu does not initially display the move down option.
Selecting a second bookmark and then de-selecting it cuases the move down option to display. So does rotating the screen.
I have no idea why this happens and no idea why it only affects German. Hopefully it is something silly in the Android build or support libraries that gets fixed with time.
Files
This also only affects my Nexus 6P running Oreo (8.0.0). It does not affect my Nexus 10 running Lolipop (5.1.1).
- Status changed from New to Closed
This bug still exists on a Nexus 6P running Android 8.1.0. But it doesn't occur on a Pixel 2 XL running Android 9. I think I am going to close this bug because it appears to be related only to the Nexus 6P and there will likely never be anything I can do about it.
- Status changed from Closed to New
- Priority changed from 2 to 3.x
I caught this bug again on my Pixel 2 XL running the 2019-01-05 security patch to Android 9. I'm going to open it back up and try to figure out what is going on.
Soren Stoutner wrote:
I caught this bug again on my Pixel 2 XL running the 2019-01-05 security patch to Android 9. I'm going to open it back up and try to figure out what is going on.
I can confirm this bug with Version 3.0.1 on a LeTV Max 2 running Omnirom Android 9. It occurs in German. I cannot confirm if it happens in other languages, too.
In all my testing it only happens in German (not any of the other languages that have translations in Privacy Browser). All the language modifications happen at the system level (meaning Android handles it all) based on text files that contain the translated text. I can't think of any reason why switching the language would cause this bug. And beyond that, I can't think of anything I could do with the code base that would fix it. It is most likely something that Google has to fix. But I can't even submit a bug report to them because I don't understand what the underlying cause it (they hardly even respond to bug reports when you can show quite clearly that it is their problem).
It also does seem to be affected by what device (or perhaps which version of Android) is running. For example, it does not happen on my Nexus 10 running Android 5.1.1 (API 22).
- Priority changed from 3.x to Next Release
- Priority changed from Next Release to 3.x
- Status changed from New to In Progress
- Priority changed from 3.x to Next Release
- Priority changed from Next Release to 3.x
Also available in: Atom
PDF
