Closed
Bug 617063
Opened 15 years ago
Closed 15 years ago
Change feedback xpi's labels/titles to match desktop firefox branding
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(fennec-)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
fennec | - | --- |
People
(Reporter: aakashd, Assigned: mfinkle)
Details
Attachments
(1 file)
3.53 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
The naming between mobile and desktop firefox is off and has led to some confusion by users and legal about how to properly identify if each is the same or not. Anyways, here's what I'd like to have changed:
...in install.rdf:
add-on name -> "Feedback"
...in feedback.dtd:
feedbackHeader.label -> "Feedback Tools"
Reporter | ||
Updated•15 years ago
|
tracking-fennec: --- → ?
Updated•15 years ago
|
tracking-fennec: ? → 2.0-
Assignee | ||
Comment 1•15 years ago
|
||
Aakash - Please verify the strings
Assignee: nobody → mark.finkle
Attachment #501912 -
Flags: review?(21)
Comment 2•15 years ago
|
||
Comment on attachment 501912 [details] [diff] [review]
patch
>diff --git a/app/profile/extensions/feedback@mobile.mozilla.org/install.rdf b/app/profile/extensions/feedback@mobile.mozilla.org/install.rdf
> <em:id>feedback@mobile.mozilla.org</em:id>
>- <em:version>1.0.0</em:version>
>+ <em:version>1.0.1</em:version>
> <em:type>2</em:type>
Just curious, what is the common practice for updating the minor number of an embedded extension? Should we update it each time there is a change in the addon or this one is done because we want the new name to be taken into account?
Attachment #501912 -
Flags: review?(21) → review+
Assignee | ||
Comment 3•15 years ago
|
||
(In reply to comment #2)
> Comment on attachment 501912 [details] [diff] [review]
> patch
>
> >diff --git a/app/profile/extensions/feedback@mobile.mozilla.org/install.rdf b/app/profile/extensions/feedback@mobile.mozilla.org/install.rdf
> > <em:id>feedback@mobile.mozilla.org</em:id>
> >- <em:version>1.0.0</em:version>
> >+ <em:version>1.0.1</em:version>
> > <em:type>2</em:type>
>
> Just curious, what is the common practice for updating the minor number of an
> embedded extension? Should we update it each time there is a change in the
> addon or this one is done because we want the new name to be taken into
> account?
No idea really. I don't have a practice myself. I just wanted bump the version somehow, since the features are being changed.
Assignee | ||
Comment 4•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•15 years ago
|
||
> Just curious, what is the common practice for updating the minor number of an
embedded extension? Should we update it each time there is a change in the
addon or this one is done because we want the new name to be taken into
account?
There isn't a common practice because this is the first time an extension is being embedded into releases. So, consider Mark the trailblazer here :).
As for the strings, looks good to me.
Comment 6•15 years ago
|
||
will await beta 4 candidate builds to verify this
Comment 7•14 years ago
|
||
Can someone please verify this bug or tell me how could I access those files: install.rdf and in feedback.dtd?
Comment 8•14 years ago
|
||
Verified fixed on:
Mozilla/5.0 (Android;Linux armv7l;rv:8.0a2)Gecko/20110908
Firefox/8.0a2 Fennec/8.0a2
Device: Samsung Galaxy S
OS: Android 2.2
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•