Closed
Bug 245385
Opened 20 years ago
Closed 15 years ago
the active theme should be selected instead of the last-selected one
Categories
(Toolkit :: Add-ons Manager, enhancement)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla1.9.3a1
Tracking | Status | |
---|---|---|
status1.9.2 | --- | beta1-fixed |
People
(Reporter: steffen.wilberg, Assigned: mossop)
References
Details
(Keywords: verified1.9.2)
Attachments
(1 file)
1.04 KB,
patch
|
robert.strong.bugs
:
review+
beltzner
:
approval1.9.2+
|
Details | Diff | Splinter Review |
While it's nice for extensions to have the one you've selected last being selected again upon opening the manager, for themes it would be better to have the active theme selected (and scrolled into view). The advantage is that you don't have to look for the current theme.
Perhaps a viable alternative to scrolling into view, would be to place the current theme either: - In its own "Current Theme" frame, at the top of the themes dialog, or - First in the list of themes
Updated•19 years ago
|
Assignee: bugs → robert.bugzilla
Updated•18 years ago
|
QA Contact: bugs → extension.manager
Updated•17 years ago
|
Assignee: robert.bugzilla → nobody
Updated•16 years ago
|
Product: Firefox → Toolkit
Assignee | ||
Updated•15 years ago
|
Target Milestone: --- → mozilla1.9.2
Assignee | ||
Comment 3•15 years ago
|
||
This is a pretty simple fix
Assignee: nobody → dtownsend
Status: NEW → ASSIGNED
Attachment #395025 -
Flags: review?(robert.bugzilla)
Updated•15 years ago
|
Attachment #395025 -
Flags: review?(robert.bugzilla) → review+
Assignee | ||
Comment 4•15 years ago
|
||
Landed: http://hg.mozilla.org/mozilla-central/rev/8cb946fd4488
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [needs baking]
Target Milestone: mozilla1.9.2 → mozilla1.9.3a1
Comment 5•15 years ago
|
||
Verified fixed with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20090821 Minefield/3.7a1pre ID:20090821030931
Status: RESOLVED → VERIFIED
Comment 6•15 years ago
|
||
Dave, how long you wanna let it bake? Seems like that we don't have any regression. Is it ready for asking approval1.9.2?
Assignee | ||
Comment 7•15 years ago
|
||
Comment on attachment 395025 [details] [diff] [review] patch rev 1 We should take this simple low-risk fix on the 1.9.2 branch
Attachment #395025 -
Flags: approval1.9.2?
Assignee | ||
Updated•15 years ago
|
Whiteboard: [needs baking]
Updated•15 years ago
|
Attachment #395025 -
Flags: approval1.9.2? → approval1.9.2+
Comment 8•15 years ago
|
||
Comment on attachment 395025 [details] [diff] [review] patch rev 1 a192=beltzner
Assignee | ||
Comment 9•15 years ago
|
||
Pushed to branch: http://hg.mozilla.org/releases/mozilla-1.9.2/rev/9fa8f9a6c12d
status1.9.2:
--- → beta1-fixed
Comment 10•15 years ago
|
||
Verified fixed on 1.9.2 with builds on OS X and Windows like Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a2pre) Gecko/20090914 Namoroka/3.6a2pre (.NET CLR 3.5.30729) ID:20090914045622 I believe we can inject this test into one of our Litmus tests.
Flags: in-litmus?
Keywords: verified1.9.2
Comment 11•13 years ago
|
||
Now covered by the following Litmus test for Firefox 3.6: https://litmus.mozilla.org/show_test.cgi?id=8168
Flags: in-litmus? → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•