Project

General

Profile

Feature #7356

Feature #7348: Improve OTR user experience

Enable formatting toolbars in Pidgin

Added by sajolida about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
06/01/2014
Due date:
% Done:

100%

Feature Branch:
feature/7356-visible-otr-status
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:
Instant Messaging

Description

Currently in Tails the status of an OTR discussion is logged in the chat and depicted in the OTR menu. I think it would be good to activate by default the Formatting Toolbars (Options → Show Formatting Toolbars) to also have to OTr button in there that explicit with words (Private/Not private) the status of an OTR conversation.

That would also make our pidgin interface consistent with the OTR documentation we are linking to at Security-in-a-Box.

As a bonus, I sometimes get some formatting enabled without willing to (things get underlined, etc.). Having this toolbar enabled by default would make the formatting options more visible.

This toolbar has been deactivated back in 2009 with commit c4a2668. I'm not sure we thought about the implications on the OTR button while doing this, and we have nothing about that either in Redmine and no mailing list archives going that far.

Associated revisions

Revision a2c7d3b6 (diff)
Added by Tails developers almost 5 years ago

Revert "$HOME: hide formatting toolbar" (Closes: #7356)

This reverts commit 5bdf66181d704dc801a68c3f1ee1343cba8290f9.

Having the formatting toolbar displayed in Pidgin is the original default, and
it makes the OTR status more explicit by displaying it with words.

Without this toolbar, the OTR status have to be inferred either from the chat
log, or from the small logo on the right of the OTR menu.

History

#1 Updated by sajolida about 5 years ago

  • Parent task set to #7348

#2 Updated by intrigeri about 5 years ago

wrote (01 Jun 2014 12:42:11 GMT) :

This toolbar has been deactivated back in 2009 with commit c4a2668. I'm not sure we
thought about the implications on the OTR button while doing this, [...]

Indeed, I very much doubt we thought about this.

#3 Updated by intrigeri about 5 years ago

  • Type of work changed from Discuss to Code

June 2014 meeting: We'll re-add it, as we could not find a reason not too, and there's a good reason to do it.

#4 Updated by intrigeri almost 5 years ago

  • Category set to 213

#5 Updated by sajolida almost 5 years ago

  • Assignee set to sajolida

#6 Updated by sajolida almost 5 years ago

  • Assignee deleted (sajolida)
  • Target version set to Tails_1.2
  • QA Check set to Ready for QA
  • Feature Branch set to feature/7356-visible-otr-status

#7 Updated by anonym almost 5 years ago

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

Merged!

#8 Updated by anonym almost 5 years ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF