Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기
Locked

Thunderbird 151.0.* doesn't accept "/" for first search of message

Mikey

I've been using T-bird since nearly the beginning, and I've always been able to search for a string in a message by hitting the slash ("/") and typing my search string. This appears to be a shortcut for Ctrl+F (on Windows, currently Windows 11).

With T-bird 151.0, when I press "/" it is ignored... the first time I use it. If I press Ctrl+F and do a search, then I can start all subsequent searches in that message with a slash. If I close that message and open another, I must again use Ctrl+F the first time I want to search.

My muscle memory constantly forces me to type "/<string>" to search, but since T-bird ignores the slash, the following characters immediately take action, usually causing me to navigate away from the message, mark them as read/unread or as junk, etc.

Since I can use "/" on subsequent searches, I'm thinking this is a bug, not a feature removal. Can this be checked/confirmed? ...thanks!

I've been using T-bird since nearly the beginning, and I've always been able to search for a string in a message by hitting the slash ("/") and typing my search string. This appears to be a shortcut for Ctrl+F (on Windows, currently Windows 11). With T-bird 151.0, when I press "/" it is ignored... the first time I use it. If I press Ctrl+F and do a search, then I can start all subsequent searches ''in that message'' with a slash. If I close that message and open another, I must again use Ctrl+F the first time I want to search. My muscle memory constantly forces me to type "/<string>" to search, but since T-bird ignores the slash, the following characters immediately take action, usually causing me to navigate away from the message, mark them as read/unread or as junk, etc. Since I can use "/" on subsequent searches, I'm thinking this is a bug, not a feature removal. Can this be checked/confirmed? ...thanks!

모든 댓글 (1)

Moderator note: this topic is being updated at https://support.mozilla.org/en-US/questions/1585474.

글쓴이 Ed 수정일시