[Meta] Prepare Tab Candy for beta4

RESOLVED WONTFIX

Status

Firefox Graveyard
Panorama
RESOLVED WONTFIX
8 years ago
2 years ago

People

(Reporter: iangilman, Unassigned)

Tracking

({meta})

Dependency tree / graph

Details

(Reporter)

Description

8 years ago
Now that we have our initial landing (bug 574217), we need to do the various things we wanted to get done before beta4. Block this bug with appropriate bugs. 

We should probably triage all of the Tab Candy component, but we can start with any bugs that are dependent on 574217. Also check out Aza's recent "state of Tab Candy" email (from Wednesday night) for other bits.

Updated

8 years ago
Depends on: 574875
(Reporter)

Updated

8 years ago
Depends on: 586721
(Reporter)

Updated

8 years ago
Depends on: 585855

Updated

8 years ago
Depends on: 586777

Updated

8 years ago
Depends on: 586814

Updated

8 years ago
Depends on: 586818

Updated

8 years ago
Depends on: 586712

Updated

8 years ago
Depends on: 586685

Updated

8 years ago
Depends on: 586719

Updated

8 years ago
Depends on: 586826

Updated

8 years ago
Depends on: 586455

Comment 1

8 years ago
From the email:

  A couple specifics:    
  - straightening out themeing issues (move JS-driven CSS to static
    files, and remaining /content vs /theme splits)
  - removal of commented out code, "TODO"s without bugs on file
  - various minor style conventions and formatting nits.

Updated

8 years ago
Depends on: 586549
(Reporter)

Updated

8 years ago
Depends on: 586834

Comment 2

8 years ago
"Tab Candy" is now "TabView" and/or "Tab Sets" ?
bug 583044

Updated

8 years ago
Depends on: 586958

Updated

8 years ago
Depends on: 586968

Updated

8 years ago
Depends on: 586943

Updated

8 years ago
Depends on: 586843

Updated

8 years ago
Depends on: 586971

Updated

8 years ago
No longer depends on: 586943

Updated

8 years ago
Depends on: 581820

Updated

8 years ago
Depends on: 586959

Updated

8 years ago
Depends on: 586992

Updated

8 years ago
Depends on: 586995

Updated

8 years ago
Depends on: 587029

Updated

8 years ago
Depends on: 587053

Updated

8 years ago
Depends on: 587054

Updated

8 years ago
Depends on: 587062

Updated

8 years ago
Depends on: 587050
No longer depends on: 587054
(Reporter)

Updated

8 years ago
Depends on: 587039

Updated

8 years ago
Depends on: 587068

Updated

8 years ago
No longer depends on: 587062

Updated

8 years ago
No longer depends on: 587050

Updated

8 years ago
No longer depends on: 586995

Updated

8 years ago
No longer depends on: 586971

Updated

8 years ago
No longer depends on: 586992

Updated

8 years ago
No longer depends on: 586843

Updated

8 years ago
No longer depends on: 586968

Updated

8 years ago
No longer depends on: 586959

Updated

8 years ago
No longer depends on: 587053
Mass moving all Tab Candy bugs from Mozilla Labs to Firefox::Tab Candy.  Filter the bugmail spam with "tabcandymassmove".
Component: TabCandy → TabCandy
Product: Mozilla Labs → Firefox
Target Milestone: -- → ---

Updated

8 years ago
Depends on: 587158
(Reporter)

Updated

8 years ago
Depends on: 587187

Updated

8 years ago
Depends on: 586971

Updated

8 years ago
Depends on: 586992

Updated

8 years ago
Depends on: 587922

Updated

8 years ago
Keywords: meta
QA Contact: tabcandy → tabcandy

Updated

8 years ago
Depends on: 587990

Updated

8 years ago
Depends on: 588394

Comment 4

8 years ago
Any status on this? Beta 4 is out and this isn't fixed, so should the fixed bugs be left on this and other bugs block another beta 5 bug? Or perhaps better just use the target milestone and track bugs instead of having this sort of meta bug that needs updating for each milestone.
can someone add bug 590563 ?
I agree with Mardak: let's use target milestones to track bugs for beta releases. Closing this as WONTFIX and removing sub-bugs which have not yet closed.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
No longer depends on: 586455, 586549, 586685, 586818, 587187, 587990, 588394
Resolution: --- → WONTFIX
(Assignee)

Updated

2 years ago
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.