Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

How to get rid of blank area at the bottom of a message window?

  • 4 trả lời
  • 2 gặp vấn đề này
  • 3 lượt xem
  • Trả lời mới nhất được viết bởi moz-sup-1

more options

Somehow (maybe since last TB upgrade) I've got at the bottom of each message a disabled text area which is impossible to get rid of (no menu entries seem to affect it). See attached picture. Even when I maximize the window, it takes up a lot of space on the screen ...

Somehow (maybe since last TB upgrade) I've got at the bottom of each message a disabled text area which is impossible to get rid of (no menu entries seem to affect it). See attached picture. Even when I maximize the window, it takes up a lot of space on the screen ...

Giải pháp được chọn

Try a restart with add-on disabled (help menu). I am not even familiar with something that fills that space, so I am guessing it is one of your add-ons. But doing the safe mode restart is always helpful with the oddities of life.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (4)

more options

Picture please. Your upload will work once you have made you initial posting (it is a bug)

more options

Here is the picture. Clicking it makes the cursor (thin vertical bar) appear in its top left corner, but the text area itself seems always disabled, context menu has the usual copy, paste, undo, etc items always disabled too. TB version 5.2.21, enabled addons are lighting 5.4.2.1, and virtual identity 0.9.33, disabled is "columns wizard" 6.0. thanks

more options

Giải pháp được chọn

Try a restart with add-on disabled (help menu). I am not even familiar with something that fills that space, so I am guessing it is one of your add-ons. But doing the safe mode restart is always helpful with the oddities of life.

more options

Hi Matt, thanks - your solution did get rid of the problem! Once the incompatible (old) version of the add-on was removed, everything was fine ... thanks again mate!