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

Windows shortcuts .lnk stopped working in Windows Firefox 137

  • Không có trả lời
  • 3 gặp vấn đề này
  • 7 lượt xem
more options

Hello, After installing Firefox 137, Windows shortcuts stopped working within Firefox: for example I am on Google Mail writing a new email. If I want to attach a file to my email, I click on the classic paper clip, it opens a windows dialog box to browse my files and folders. Up to now, if I did double-click on a shortcut (a .lnk file) it would follow the shortcut (like if it was a folder shortcut it would open the corresponding folder) for me to choose a file ... As of 137 it attaches the shortcut, and tries to attach the whole content of the folder ! I tried the same operation on Chrome, it works ok. I tried the same operation on a different service on Firefox (Mattermost) I have the same problem, so my guess is that the problem is with Firefox 137. (this has been working properly for the last 10 years at least). And I made the test on MacOS, no problem, it's really with Firefox 137 on Windows. Anybody else seeing this ?

Hello, After installing Firefox 137, Windows shortcuts stopped working within Firefox: for example I am on Google Mail writing a new email. If I want to attach a file to my email, I click on the classic paper clip, it opens a windows dialog box to browse my files and folders. Up to now, if I did double-click on a shortcut (a .lnk file) it would follow the shortcut (like if it was a folder shortcut it would open the corresponding folder) for me to choose a file ... As of 137 it attaches the shortcut, and tries to attach the whole content of the folder ! I tried the same operation on Chrome, it works ok. I tried the same operation on a different service on Firefox (Mattermost) I have the same problem, so my guess is that the problem is with Firefox 137. (this has been working properly for the last 10 years at least). And I made the test on MacOS, no problem, it's really with Firefox 137 on Windows. Anybody else seeing this ?

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.