Closed Bug 954651 Opened 11 years ago Closed 6 years ago

Cleanup the account.xml binding

Categories

(Instantbird Graveyard :: Account manager, defect)

defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: florian, Unassigned)

References

Details

(Whiteboard: [1.6-wanted])

Attachments

(1 file)

*** Original post on bio 1219 at 2012-01-02 22:36:00 UTC *** It should use only one label or description tag, instead of the 4 label + 2 description we currently have. (This should also fix bug 953661 (bio 215))
Blocks: 954598
*** Original post on bio 1219 at 2012-01-24 12:23:56 UTC *** I would also like us to change the icon showed for error message depending on the message. Currently we add the yellow warning icon when there's a connection error. I think we could use 3 different icons for info message (eg. "Entering a password will be required to connect this account"), errors and fatal errors (eg. "No ... protocol plugin."). The icons for this are at: chrome://global/skin/icons/information-16.png chrome://global/skin/icons/warning-16.png (already used) chrome://global/skin/icons/error-16.png
Whiteboard: [1.2-wanted]
*** Original post on bio 1219 as attmnt 1129 at 2012-01-24 13:05:00 UTC *** What about the password-related 'key'-icon that people might know from Firefox already for the password-required message? I can't find it in mxr, so here's a screenshot attached.
*** Original post on bio 1219 at 2012-04-05 17:29:12 UTC *** Also, use only one button for the connect/disconnect actions and change the label. This would hide/fix bugs like bug 954771 (bio 1338).
Depends on: 954930
Whiteboard: [1.2-wanted] → [1.3-wanted]
*** Original post on bio 1219 at 2012-08-02 18:14:35 UTC *** Also, the UI changes required following the changed connection behaviour from bug 954930 (bio 1497) (see in particular comment #4 there).
*** Original post on bio 1219 at 2012-08-02 18:44:13 UTC *** (In reply to comment #4) Since that link didn't work: - Ci.imIAccountsService.AUTOLOGIN_START_OFFLINE is obsolete: we no longer try to connect when the status or necko are offline. - The user should be able to distinguish whether it's just the status that is offline, or that necko is offline. - The user should be able to tell which accounts will automatically (re)connect when next online. - The "connect"/"disconnect" buttons should (possibly) remain enabled in the account manager even when the status is OFFLINE. Clicking "connect" while offline would then just change the message from "Not connected" to "Will be connected when leaving the offline status".
*** Original post on bio 1219 at 2012-11-05 23:34:40 UTC *** Realistically, this isn't going to be ready for 1.3, moving to 1.4-wanted.
Whiteboard: [1.3-wanted] → [1.4-wanted]
*** Original post on bio 1219 at 2012-11-08 22:33:59 UTC *** Maybe also find a way to stop an account trapped in a reconnection attempt loop from reconnecting. This happens when the connection attempts fail too quickly to allow the user to explicitly disconnect.
*** Original post on bio 1219 at 2012-11-12 13:27:55 UTC *** (In reply to comment #7) > Maybe also find a way to stop an account trapped in a reconnection attempt loop > from reconnecting. This happens when the connection attempts fail too quickly > to allow the user to explicitly disconnect. It's since been pointed out to me that "cancel reconnections" exists in the context menu. I think it would be better for this to be the button state when a reconnection attempt is pending. I.e. the button would be "Cancel reconnections", and then "Connect" when clicked. This is more discoverable and doesn't really slow down a user who wants to immediately reconnect (he just clicks twice).
*** Original post on bio 1219 at 2012-11-12 13:48:41 UTC *** (In reply to comment #8) > This is more discoverable and doesn't really slow down > a user who wants to immediately reconnect (he just clicks twice). I would never think of clicking on a "cancel reconnections" button to reconnect. It's a bit like clicking a "start" button to turn off a computer ;).
Blocks: 954248
*** Original post on bio 1219 at 2013-04-09 14:50:02 UTC *** s/1.4-wanted/1.5-wanted/ in the whiteboard for bugs that probably won't happen before 1.4 is released.
Whiteboard: [1.4-wanted] → [1.5-wanted]
*** Original post on bio 1219 at 2013-11-02 17:41:55 UTC *** Mass changing bugs from 1.5-wanted -> 1.6-wanted.
Whiteboard: [1.5-wanted] → [1.6-wanted]
On the behalf of Florian: Closing bugs related to the Instantbird UI as WONTFIX, as the development of the standalone chat client Instantbird has stopped. Instantbird users are encouraged to migrate to Thunderbird. The user interface of instant messaging in Thunderbird will feel familiar, as the Thunderbird IM support started as a fork of Instantbird.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
On the behalf of Florian: Closing bugs related to the Instantbird UI as WONTFIX, as the development of the standalone chat client Instantbird has stopped. Instantbird users are encouraged to migrate to Thunderbird. The user interface of instant messaging in Thunderbird will feel familiar, as the Thunderbird IM support started as a fork of Instantbird.
On the behalf of Florian: Closing bugs related to the Instantbird UI as WONTFIX, as the development of the standalone chat client Instantbird has stopped. Instantbird users are encouraged to migrate to Thunderbird. The user interface of instant messaging in Thunderbird will feel familiar, as the Thunderbird IM support started as a fork of Instantbird.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: