| Summary: |
Connection no longer enforces legal state transitions |
| Product: |
Telepathy
|
Reporter: |
Simon McVittie <smcv> |
| Component: |
tp-qt | Assignee: |
Telepathy bugs list <telepathy-bugs> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Telepathy bugs list <telepathy-bugs> |
| Severity: |
normal
|
|
|
| Priority: |
medium
|
|
|
| Version: |
unspecified | |
|
| Hardware: |
Other | |
|
| OS: |
All | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
15:27 < smcv> I notice onStatusChanged() no longer forces legal state transitions 15:27 < smcv> it used to pretend Disconnected -> Connected was Disconnected -> Connecting -> Connected 15:28 < andrunko> ah yes, I removed this 15:28 < smcv> (to reduce the number of possible code paths for clients - tp-glib enforces the same on the CM side, but you can still get the illegal state transition from e.g. Python CMs) 15:28 < smcv> why? can we have it back? 15:28 < andrunko> I can add it back, yes 15:29 < andrunko> I removed when developing and then forgot to re-add Not a merge blocker IMO, so I'm filing a bug instead.