Closed
Bug 871514
Opened 11 years ago
Closed 11 years ago
Replace "click" with "touch" on About:firefox update button
Categories
(Firefox for Android Graveyard :: Theme and Visual Design, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 24
People
(Reporter: ibarlow, Assigned: stully)
Details
(Whiteboard: [mentor=kats][good first bug])
Attachments
(1 file, 1 obsolete file)
3.16 KB,
patch
|
kats
:
review+
|
Details | Diff | Splinter Review |
When tapping the "check for updates button", the string that comes back reads "Update available; click to download" or "Update available; click to install" We shouldn't be using the word "click" on Android, let's change it to "tap".
Comment 1•11 years ago
|
||
This was added in bug 827347 because there is no concept of tapping on Ouya.
Reporter | ||
Comment 2•11 years ago
|
||
Ah, I was wondering what brought about the change... Can we special case the Ouya builds, then so that they don't affect devices with touch screens?
Reporter | ||
Comment 3•11 years ago
|
||
Updating title -- for consistency with our updater we should use touch, not tap.
Summary: Replace "click" with "tap" on About:firefox update button → Replace "click" with "touch" on About:firefox update button
Comment 4•11 years ago
|
||
I want to give Kats a chance to respond since he championed the change. I do think Ouya has a touchpad on the controller, so "touch" or "tap" might not be as foreign to those users.
Comment 5•11 years ago
|
||
While the Ouya controller does have a touchpad, it is used to control a mouse cursor that appears on the screen, so I think using "click" is the most appropriate for that scenario. Using "tap" might be ok there too, but "touch" doesn't feel right for that scenario. If we absolutely want to use "touch" or "tap" for touch-enabled devices I'm not opposed to special-casing this.
Reporter | ||
Comment 6•11 years ago
|
||
Hm, or we could just change the string everywhere to read "Download update" when one is available
Comment 7•11 years ago
|
||
That sounds good to me. There's another message that shows up after the update is downloaded that says "Updated downloaded; click to install" - I assume we should change that to "Install update" as well.
Comment 8•11 years ago
|
||
Trivial string changes make for good first bugs :) The strings are located in mobile/android/locales/en-US/chrome/about.dtd.
OS: Mac OS X → Android
Hardware: x86 → All
Whiteboard: [mentor=kats][good first bug]
Comment 9•11 years ago
|
||
Hi, I'd like to get involved with FireFox Mobile, figure this would be a good first bug. Mind if I assign this one to myself?
Comment 10•11 years ago
|
||
(In reply to alexchan7432 from comment #9) > Hi, > I'd like to get involved with FireFox Mobile, figure this would be a good > first bug. Mind if I assign this one to myself? Go ahead. For some information on building Firefox on Android, see: https://wiki.mozilla.org/Mobile/Fennec/Android For realtime chatting with other developers, visit #mobile on Mozilla's IRC server: http://irc.mozilla.org
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → stully
Assignee | ||
Comment 11•11 years ago
|
||
Changed updates available and updates downloaded strings as described in comments.
Attachment #752955 -
Flags: review?(bugmail.mozilla)
Comment 12•11 years ago
|
||
Comment on attachment 752955 [details] [diff] [review] change strings as described in comments Review of attachment 752955 [details] [diff] [review]: ----------------------------------------------------------------- After double-checking the string change procedure [1] (I haven't had to do this very often) it looks like we'll have to update the entity names as well. So for example you can change aboutPage.checkForUpdates.available to aboutPage.checkForUpdates.available2 in the dtd file and update the references to it in about.xhtml as well. Also please make sure your patch includes a commit message as per [2] [1] https://developer.mozilla.org/en-US/docs/Making_String_Changes [2] https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F
Attachment #752955 -
Flags: review?(bugmail.mozilla) → review-
Assignee | ||
Updated•11 years ago
|
Attachment #752955 -
Attachment is obsolete: true
Assignee | ||
Comment 13•11 years ago
|
||
Change string entity names and reflect changes in about.xhtml (and added commit message; sorry!)
Attachment #752996 -
Flags: review?(bugmail.mozilla)
Comment 14•11 years ago
|
||
Comment on attachment 752996 [details] [diff] [review] 02 Remove "click" from update strings to accomodate touch devices Review of attachment 752996 [details] [diff] [review]: ----------------------------------------------------------------- Looks good, thanks!
Attachment #752996 -
Flags: review?(bugmail.mozilla) → review+
Updated•11 years ago
|
Keywords: checkin-needed
Comment 15•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/48b38e667074
Keywords: checkin-needed
Comment 16•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/48b38e667074
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 24
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•