Closed
Bug 1020459
Opened 10 years ago
Closed 8 years ago
Avoid re-entrancy in requestAutocomplete calls
Categories
(Toolkit :: Form Manager, defect)
Toolkit
Form Manager
Tracking
()
RESOLVED
INVALID
People
(Reporter: Paolo, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [diamond])
If a requestAutocomplete request is already active, we should ensure that the request mechanism itself is not re-entered, so that we don't generate double responses. The specification draft is still unclear about this case, because it requires an asynchronous "disabled" rAc event to be dispatched in this case, which cannot be distinguished from the event resulting from the first requestAutocomplete call.
Reporter | ||
Updated•10 years ago
|
Flags: firefox-backlog+
Updated•10 years ago
|
Whiteboard: p=5 → p=5 [qa?]
Reporter | ||
Updated•10 years ago
|
Whiteboard: p=5 [qa?] → p=5 [qa-]
Comment 1•10 years ago
|
||
Flagging diamond. Paolo, would you be willing to mentor this one?
Flags: needinfo?(paolo.mozmail)
Whiteboard: p=5 [qa-] → p=5 [qa-] [diamond]
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Mike Hoye [:mhoye] from comment #1) > Flagging diamond. Paolo, would you be willing to mentor this one? At present, this bug is not actionable because the infrastructure it depends on is not in place. We're not keeping track of this using normal dependencies because the project is at its initial stages and the dependencies between individual implementation bugs tend to shift a lot. I believe that all unassigned bugs blocking rAc-one are in a similar state.
Flags: needinfo?(paolo.mozmail)
Comment 3•10 years ago
|
||
(In reply to :Paolo Amadini from comment #2) > (In reply to Mike Hoye [:mhoye] from comment #1) > > Flagging diamond. Paolo, would you be willing to mentor this one? > > At present, this bug is not actionable because the infrastructure it depends > on is not in place. > > We're not keeping track of this using normal dependencies because the > project is at its initial stages and the dependencies between individual > implementation bugs tend to shift a lot. I believe that all unassigned bugs > blocking rAc-one are in a similar state. If this isn't actionable right now, can we remove it from the backlog?
Flags: needinfo?(mmucci)
Comment 4•10 years ago
|
||
Removed based on Comment #2.
Flags: needinfo?(mmucci)
Flags: firefox-backlog+
Whiteboard: p=5 [qa-] [diamond] → [diamond]
Reporter | ||
Comment 5•10 years ago
|
||
We should keep the point estimate since this helps us tracking the overall requestAutocomplete "milestone one" effort, which we're tracking here: https://mnoorenberghe.github.io/rac-bugs/?list=rAc-one&maxdepth=1
Whiteboard: [diamond] → p=5 [diamond]
Updated•10 years ago
|
Comment 6•8 years ago
|
||
requestAutocomplete was removed from the HTML specification.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•