The default bug view has changed. See this FAQ.

The "minutes of inactivity" text is cut in the Chat prefpane

RESOLVED FIXED in Thunderbird 14.0

Status

Thunderbird
Instant Messaging
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: florian, Assigned: florian)

Tracking

Trunk
Thunderbird 14.0

Thunderbird Tracking Flags

(thunderbird13 fixed)

Details

Attachments

(2 attachments)

(Assignee)

Description

5 years ago
Created attachment 607952 [details] [diff] [review]
Patch

This is because the textbox is way too big.
Attachment #607952 - Flags: review?(bwinton)
(Assignee)

Updated

5 years ago
Duplicate of this bug: 739272
Comment on attachment 607952 [details] [diff] [review]
Patch

I like it, although I wonder if you should set a maximum for the timeBeforeAway, just to make sure it'll fit in 4em…

Either way, r=me.

Thanks,
Blake.
Attachment #607952 - Flags: review?(bwinton) → review+
(Assignee)

Comment 3

5 years ago
(In reply to Blake Winton (:bwinton - Thunderbird UX) from comment #2)
[...]
> I wonder if you should set a maximum for the
> timeBeforeAway, just to make sure it'll fit in 4em…

We have just discussed this on IRC are decided to use max=720 (720 minutes = 12 hours).
(Assignee)

Comment 4

5 years ago
Created attachment 610050 [details] [diff] [review]
As checked in
Assignee: nobody → florian
(Assignee)

Comment 5

5 years ago
http://hg.mozilla.org/comm-central/rev/b51b991976bf
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 14.0
(Assignee)

Comment 6

5 years ago
Comment on attachment 610050 [details] [diff] [review]
As checked in

[Approval Request Comment]
This fixes a piece of obviously broken UI in the Chat prefpane, so we should take it on aurora.
Attachment #610050 - Flags: approval-comm-aurora?

Updated

5 years ago
Attachment #610050 - Flags: approval-comm-aurora? → approval-comm-aurora+
(Assignee)

Comment 7

5 years ago
http://hg.mozilla.org/releases/comm-aurora/rev/c8aad79c9c16
status-thunderbird13: --- → fixed
You need to log in before you can comment on or make changes to this bug.