Closed Bug 1026814 Opened 6 years ago Closed 6 years ago
Arabic language selection pushes icons off of vertical homescreen
Before you attempt to repro, be aware that you may not be able to recover from this bug and may need to re-flash your phone to get out of this state. Restarting doesn't work because the language setting holds. In the latest 2.0 build: * Select Arabic language on set-up/FTE or change to Arabic in language settings. * Observe Homescreen icons shift right, leaving one vertical row of icons aligned right. If the user selected Arabic in FTE, this is all s/he will ever see of the Homescreen (they won't necessarily know anything is wrong or why). * Note that the Settings icon may not be visible/included in the single vertical row. If the Settings icon is not there, there is no way (since pinch-to-zoom has been taken out) for the user to access the Settings icon in order to be able to click on it and change the language setting to recover the full homescreen (which a normal user would not know to do anyway). Until we have RTL support, we should not include languages in FTE that users can choose, that will result in this outcome. Believe this should block since it renders the device unusable. It's very easy to hit Arabic accidentally (it's in the top-most section of the list) if you're rapidly clicking through to be done with FTE.
Can we remove RTL languages for our 2.0 builds?
Flags: needinfo?(jlorenzo) → needinfo?(l10n)
I don't think we should block on this. Trying to support RTL in the vertical homescreen at this point would be way too much work.
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-]
(In reply to Jason Smith [:jsmith] from comment #3) > I don't think we should block on this. Trying to support RTL in the vertical > homescreen at this point would be way too much work. Or should say - it's not in scope for 2.0 release.
I think the issue here isn't that that we're not going to support Arabic. As Stephany says, the issue "renders the device unusable. It's very easy to hit Arabic accidentally (it's in the top-most section of the list) if you're rapidly clicking through to be done with FTE." If a user accidentally hits Arabic during FTE, then he won't be able to revert and switch back to another language (at least, that's what I understand)
I am not sure if we can support RTL, but we should certainly make sure it doesn't break things. Taking this.
Assignee: nobody → kgrandon
Status: NEW → ASSIGNED
If someone has time to fix this after all of the blockers, we can revisit it, but for now we should disable RTL support I think until it's working. Cristian - do you have time for a review?
Attachment #8441840 - Flags: review?(crdlc)
Comment on attachment 8441840 [details] [review] Github pull request LGTM, go ahead
Attachment #8441840 - Flags: review?(crdlc) → review+
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Removing languages from the builds is going to throw us back ages on those localizations, we should not do that. Also, please only use email@example.com for l10n work, I don't want to get all this bugmail twice. I'd suggest that once we get this verified, we should request uplift to 2.0. Also, there's a pseudo localization, qps-plocm (Mirrored English), please make sure to test-drive at least basic functionality when changing gaia.
Comment on attachment 8441840 [details] [review] Github pull request This is needed for the vertical homescreen. We've done our best effort at testing this and believe it is safe for uplift.
Attachment #8441840 - Flags: approval-gaia-v2.0?(bbajaj)
Attachment #8441840 - Flags: approval-gaia-v2.0?(bbajaj) → approval-gaia-v2.0+
Verified Fixed. Issue no longer occurs in Flame 2.1 or 2.0 All icons are visible and usable on Homescreen when using Arabic Language selection. Environmental Variables: Device: Flame 2.1 BuildID: 20140915000203 Gaia: 944e5b4582c4efa1b67cd33245dbb8f6aa25d09f Gecko: 7546fedad918 Version: 34.0a2 (2.1) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Environmental Variables: Device: Flame 2.0 BuildID: 20140915000202 Gaia: 7edd3b0b9f65c3dde235c732d270e43e055a1254 Gecko: 13e04ab68621 Version: 32.0 (2.0) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?][VH-FL-blocking-][VH-FC-blocking-] → [QAnalyst-Triage+][VH-FL-blocking-][VH-FC-blocking-]
You need to log in before you can comment on or make changes to this bug.