Closed Bug 533019 Opened 10 years ago Closed 10 years ago

Default Browser setting: Make strings localizable

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Windows Mobile 6 Professional
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alexp, Assigned: alexp)

References

()

Details

Attachments

(1 file)

Move hard-coded strings from browser.xul to preferences.dtd as it was originally.
Attached patch FixSplinter Review
Attachment #416188 - Flags: review?(mark.finkle)
Assignee: nobody → alexp
This patch looks good, but it cannot land until mobile-browser is branched or Fennec 1.0 is released. Therefore, I won't r+ until either of those situations occurs.
Can we land this one now?
Attachment #416188 - Flags: review?(mark.finkle) → review+
(In reply to comment #3)
> Can we land this one now?

Not quite yet, but soon. We have other patches waiting too.
Whiteboard: [fennec-checkin-post1.0]
Status: NEW → ASSIGNED
pushed:
http://hg.mozilla.org/mobile-browser/rev/85f85d86b25b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fennec-checkin-post1.0]
We're branched?
(In reply to comment #6)
> We're branched?

Nope. Fennec 1.0 has been shipped and we have a release tag in Hg we will build from if we need to release a security fix.
Guys, I have no idea what I'm supposed to do with this.

Does string freeze mean anything to you?
Component: Windows Mobile → General
QA Contact: mobile-windows → general
You need to log in before you can comment on or make changes to this bug.