Closed
Bug 294129
Opened 20 years ago
Closed 18 years ago
[Meta] Tracking bug for issues that cause the UI to lock or get into a blocked state
Categories
(Camino Graveyard :: General, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
Camino1.5
People
(Reporter: samuel.sidler+old, Unassigned)
References
Details
(Keywords: meta)
This is a meta tracking bug for locked state issues.
Comment 1•20 years ago
|
||
What are "locked state issues"?
(In reply to comment #1) > What are "locked state issues"? Based on the bugs Samuel started this bug with, it's "interface lock" where Camino gets locked up (not hung per se) because one part of the UI has "focus" but is hidden inaccessible...somehow having two modal elements up at once. At least that's what I thought he was going for and filled in the rest of the bugs from my list....
| Reporter | ||
Comment 3•20 years ago
|
||
Simon: See *your* comment 6 on bug 157715. ;)
Updated•20 years ago
|
Summary: [Meta] Tracking bug for locked state issues → [Meta] Tracking bug for issues that cause the UI to get into a blocked state
| Reporter | ||
Comment 4•20 years ago
|
||
Adding "lock" to the description for easier searching.
Summary: [Meta] Tracking bug for issues that cause the UI to get into a blocked state → [Meta] Tracking bug for issues that cause the UI to lock or get into a blocked state
Depends on: 232818
Depends on: 200397
Updated•19 years ago
|
Priority: -- → P2
Target Milestone: --- → Camino1.0
Depends on: 315697
Depends on: 318166
Simon, can you decide which of these need to be fixed for 1.0 and which can wait? There are two differnt bugs that are caused at startup in bug 314072, and it's plussed already.
Flags: camino1.0?
Comment 6•19 years ago
|
||
I'm tempted to remove the "set camino as default" dialog, as I've seen too many people swear at it.
Moving off per irc.
Flags: camino1.0? → camino1.0-
Target Milestone: Camino1.0 → Camino1.1
Comment 8•19 years ago
|
||
On 10.4, having fixed bug 314072, I can't cause Camino to get into a locked state via any of the bugs linked here.
No longer depends on: 225276
Once 1.0 ships, we can close bug 157715, bug 232818, and bug 287784 as WFM, since they don't cause locked states on 10.3.9 or 10.4.x any more.
Comment 10•18 years ago
|
||
(In reply to comment #8) > On 10.4, having fixed bug 314072, I can't cause Camino to get into a locked > state via any of the bugs linked here. I can confirm this with the remaining open bugs (bug 181721 and bug 189298) as of today, using the 2006110822 trunk nightly. (I don't recall ever being able to get into a locked state as a result of 181721 in the first place.) cl
Assignee: mikepinkerton → nobody
QA Contact: general
Comment 11•18 years ago
|
||
Since of the two bugs currently left here one has a patch posted and the other is now 2.0, it's probably time to close or punt this
Comment 12•18 years ago
|
||
Sounds good. undepping remaining open bugs (bug 181721 and bug189298) and closing FIXED.
| Reporter | ||
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•