Closed
Bug 866208
Opened 13 years ago
Closed 5 years ago
Polish the label of DoNotTrack settings after Bug 863242
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: tetsuharu, Unassigned)
References
Details
Attachments
(1 file)
|
3.08 KB,
patch
|
mfinkle
:
review-
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #863242 +++
After Bug 863242, We might need to polish the label of DoNotTrack settings for L10n & usability.
| Reporter | ||
Comment 1•13 years ago
|
||
I think we need to fix this before merge central 23 to aurora 23. It will be string freeze.
Ping: Ian
Flags: needinfo?(ibarlow)
| Reporter | ||
Comment 2•13 years ago
|
||
At next Monday, we will merge to aurora 23 and do string freeze. But the current label of DNT setting for Fennec isn't friendly for L10n.We must change labels immediately before merge working.
I think this patch is provisional. We need to think more better labels in next 6 weeks for ver.24.
And, I propose we should land this patch on mozilla-central directly.
Attachment #748548 -
Flags: review?(mark.finkle)
Comment 3•13 years ago
|
||
Comment on attachment 748548 [details] [diff] [review]
patch to polish labels
I don't want to rush things too much.
The current strings are a little long, but I think they are better than the short strings.
Let's get UX to create some ideas. We might be able to push these to aurora if we ask nicely and do it quickly.
Attachment #748548 -
Flags: review?(mark.finkle) → review-
Comment 4•13 years ago
|
||
Sorry for the delay here, Matej our copywriter and I keep missing eachother...
Keep in mind though that when we change them, it is unlikely that we will shorten them too much, and they may still wrap onto two lines. Explaining the differences between the three options for tracking in a concise manner isn't easy, so I don't want to set an expectation that we can just cut the copy in half and still make it work.
Will post updated strings as soon as we can.
Flags: needinfo?(ibarlow)
| Reporter | ||
Comment 5•13 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #3)
> Comment on attachment 748548 [details] [diff] [review]
> patch to polish labels
>
> I don't want to rush things too much.
>
> The current strings are a little long, but I think they are better than the
> short strings.
>
> Let's get UX to create some ideas. We might be able to push these to aurora
> if we ask nicely and do it quickly.
OK. I understand.
(In reply to Ian Barlow (:ibarlow) from comment #4)
> Sorry for the delay here, Matej our copywriter and I keep missing
> eachother...
>
> Keep in mind though that when we change them, it is unlikely that we will
> shorten them too much, and they may still wrap onto two lines. Explaining
> the differences between the three options for tracking in a concise manner
> isn't easy, so I don't want to set an expectation that we can just cut the
> copy in half and still make it work.
>
> Will post updated strings as soon as we can.
Thank you, Ian.
I entrust this work to you.
Comment 6•13 years ago
|
||
To clarify, whatever changes we make to these strings can come in a later release. They shouldn't block us uplifting what we have into Aurora.
Comment 7•5 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•5 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
•