Closed
Bug 458205
Opened 16 years ago
Closed 15 years ago
[meta] Cocoa widget regressions blocking release
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino2.0
People
(Reporter: stuart.morgan+bugzilla, Unassigned)
Details
We have a number of core regressions that need to be fixed on the 1.9.0 branch before we can realistically ship Camino 2, so we should have a place to track them (as Smokey has been pointing out for a while).
Feel free to suggest other blockers, but only if they are serious enough that they would affect our ability to release 2.0.
Reporter | ||
Updated•16 years ago
|
Comment 1•16 years ago
|
||
Won't block 2.0a1, obviously, but should this block b1? (I assume the release is a yes, but nominating to be sure.)
Flags: camino2.0b1?
Flags: camino2.0?
Hardware: PC → All
Reporter | ||
Comment 3•16 years ago
|
||
Removing 459744; 462234 will cover it.
No longer depends on: 459744
Reporter | ||
Comment 4•16 years ago
|
||
Removing bug 433719 and bug 442245 since they have landed on the 1.9.0 branch (removing since FIXED doesn't actually give us useful information given that FIXED for a core bug means 1.9.1)
Reporter | ||
Comment 5•15 years ago
|
||
Bug 458961 landed on 1.9.0, so removing that too.
Since it looks like 412223 isn't going anywhere, and doesn't seem to be hammering people any more (given that reports of it have dropped off), it may be time to close this, but we'll give it a bit longer and see how things go with b3.
No longer depends on: 458961
Reporter | ||
Comment 6•15 years ago
|
||
I think we'll call this good. 412223 isn't a blocker any more, and the only core change we'd still really like for 2.0 (key event propagation) is basically tracked by the delete/esc bugs.
Flags: camino2.0? → camino2.0-
You need to log in
before you can comment on or make changes to this bug.
Description
•