Obsolete
Status Update
Comments
dn...@google.com <dn...@google.com>
dn...@google.com <dn...@google.com> #2
We have passed this to the development team and will update this issue with more information as it becomes available.
lb...@gmail.com <lb...@gmail.com> #3
@2 I think it's too late. Android O is now final. The issues are there.
I tried to tell you to delay the Android O release, because I did find various bugs and was sure there are more that I can find.
I tried to tell you to delay the Android O release, because I did find various bugs and was sure there are more that I can find.
dn...@google.com <dn...@google.com> #4
Following are the observations:
->Issue shown in 1.png screenshot is resolved in our internal latest build.
Fix will be available to public in future releases.
->2.png screenshot shows trademarked names "Google Play Protect", "Nexus Imprint", and "Smart Lock" not being translated - we typically don't translate trademarked terms so this is working as intended.
->4.png screenshot shows 2 issues:
-the "on body detection" icon not being reversed - none of the other ones such as connected devices, etc. are and this one isn't particularly directional, so this is working as intended.
-text at the end of the Wifi substring (wifi, mobile, data usage, hotspot) being truncated, and noting that there is room to overflow to a second line. We don't typically do overflow, at least at this level of the settings hierarchy, so this is working as intended.
->5.png screenshot attached in comment #1 has 3 issues:
-LTE/H/E overlap over the icon:
This is observed on reported build(OPP4.170623.014) and android O final release(OPR6.170623.013).
But issue is resolved in internal latest OPM1.170822.001 build.
Fix will be available to public in future releases.
-Network operator name as shown in the screenshot appears close to battery symbol:
Engineering team is analyzing this bug.
-Portrait text translation issue:
Engineering team is analyzing this bug.
->Issue shown in 1.png screenshot is resolved in our internal latest build.
Fix will be available to public in future releases.
->2.png screenshot shows trademarked names "Google Play Protect", "Nexus Imprint", and "Smart Lock" not being translated - we typically don't translate trademarked terms so this is working as intended.
->4.png screenshot shows 2 issues:
-the "on body detection" icon not being reversed - none of the other ones such as connected devices, etc. are and this one isn't particularly directional, so this is working as intended.
-text at the end of the Wifi substring (wifi, mobile, data usage, hotspot) being truncated, and noting that there is room to overflow to a second line. We don't typically do overflow, at least at this level of the settings hierarchy, so this is working as intended.
->5.png screenshot attached in
-LTE/H/E overlap over the icon:
This is observed on reported build(OPP4.170623.014) and android O final release(OPR6.170623.013).
But issue is resolved in internal latest OPM1.170822.001 build.
Fix will be available to public in future releases.
-Network operator name as shown in the screenshot appears close to battery symbol:
Engineering team is analyzing this bug.
-Portrait text translation issue:
Engineering team is analyzing this bug.
lb...@gmail.com <lb...@gmail.com> #5
@4
1. ok . I think another system notification didn't change as well.
2. This means that people who can't read English, can't understand what it means. The whole point of switching locale, is to be able to read and understand what everything means, even if you don't know English. "Smart Lock" is the best example of what I'm talking about. All it says in Hebrew below it, is just "in order to use this feature, first set screen lock".
It doesn't provide any clue about what it is.
At least in English, it gives you a clue: it makes the locking smarter (though I think a better name would be "Smart Unlock" instead, because it doesn't lock, it unlocks).
3. ?
4. The text is truncated, so nobody can read it, even in English. Why have preferences that even in normal display can't be read ? What's the point of having content that can't be read?
I think all preferences should be possible to read. You should add a new UX rule for this.
5. Thanks. What about the weird translation?
6. ?
1. ok . I think another system notification didn't change as well.
2. This means that people who can't read English, can't understand what it means. The whole point of switching locale, is to be able to read and understand what everything means, even if you don't know English. "Smart Lock" is the best example of what I'm talking about. All it says in Hebrew below it, is just "in order to use this feature, first set screen lock".
It doesn't provide any clue about what it is.
At least in English, it gives you a clue: it makes the locking smarter (though I think a better name would be "Smart Unlock" instead, because it doesn't lock, it unlocks).
3. ?
4. The text is truncated, so nobody can read it, even in English. Why have preferences that even in normal display can't be read ? What's the point of having content that can't be read?
I think all preferences should be possible to read. You should add a new UX rule for this.
5. Thanks. What about the weird translation?
6. ?
dn...@google.com <dn...@google.com> #6
Engineering team is analyzing issues shown in 3.png , 6.png and weird translation issue in 5.png.
lb...@gmail.com <lb...@gmail.com> #7
@6 Thank you.
About #4 :
"-the "on body detection" icon not being reversed - none of the other ones such as connected devices, etc. are and this one isn't particularly directional, so this is working as intended."
This is actually weird and confusing, because "mobile data" (cellular networks) isn't reversed, while on the notification drawer it is.
Attached image to show this issue.
Since on English you look at things from left to right, the person looks fine walking in this direction, but on Hebrew, things are from right to left, so it's weird. I think it should be the opposite. Even on traffic lights and signs in Israel we see it in the opposite direction. Exampleד:
https://www.youtube.com/watch?v=NtscMcGbSXY
http://www.autocom.co.il/Betichut/safety1/git.aspx
About #4 :
"-the "on body detection" icon not being reversed - none of the other ones such as connected devices, etc. are and this one isn't particularly directional, so this is working as intended."
This is actually weird and confusing, because "mobile data" (cellular networks) isn't reversed, while on the notification drawer it is.
Attached image to show this issue.
Since on English you look at things from left to right, the person looks fine walking in this direction, but on Hebrew, things are from right to left, so it's weird. I think it should be the opposite. Even on traffic lights and signs in Israel we see it in the opposite direction. Exampleד:
dn...@google.com <dn...@google.com> #8
We have passed this information to engineering team.
dn...@google.com <dn...@google.com> #9
We have deferred this to a future release, but leaving this open for now.
is...@google.com <is...@google.com>
sa...@google.com <sa...@google.com> #10
We will be closing this bug due to being logged in a Preview version of Android. If the issue is still relevant and reproducible in the latest public release (Android Q), please capture a bugreport and log the bug in https://goo.gl/TbMiIO . If a reply is not received within the next 14 days, this issue will be closed. Thank you for your understanding.
Description
OPP4.170623.014
* What device are you using? (for example, Nexus 6P)
Nexus 5x
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Switch to Hebrew ("עברית") locale, and look around...
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
UX
* What was the expected result?
To see good, consistent alignment of UI components, without overlapping of them.
* What was the actual result?
In many cases, it's quite easy to find issues.
I'm sure that I can find more, even on Google's apps.
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)
Attached all, including my comments on each