Open
Bug 1368784
Opened 7 years ago
Updated 2 years ago
[meta] rethink the event coalescence system
Categories
(Core :: Disability Access APIs, enhancement, P2)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: surkov, Unassigned)
References
(Depends on 3 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta, Whiteboard: qa-not-actionable)
We've got a new event coalescence system in bug 1270916 which regressed us in * numerous of security and stability bugs (see bug 1362057) (hot fix from bug 1363027 is applied to stop bleeding) * preformance, see bug 1360160 We need to analyze carefully this system and the retired one (EventTree), and figure out a working solution.
Reporter | ||
Updated•7 years ago
|
Severity: normal → critical
Priority: -- → P1
Updated•7 years ago
|
Priority: P1 → P3
Reporter | ||
Comment 1•7 years ago
|
||
David, I believe this shouldn't go into the backlog as a stability/perf/correctness improvement, if it's not addressed by the next release, then we should make sure this is a candidate next to it.
Priority: P3 → P2
Updated•3 years ago
|
Whiteboard: qa-not-actionable
Updated•3 years ago
|
Summary: rethink the event coalescence system → [meta] rethink the event coalescence system
Comment 2•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: critical → --
You need to log in
before you can comment on or make changes to this bug.
Description
•