Trang web này sẽ có chức năng hạn chế trong khi chúng tôi trải qua bảo trì để cải thiện trải nghiệm của bạn. Nếu một bài viết không giải quyết được vấn đề của bạn và bạn muốn đặt câu hỏi, chúng tôi có cộng đồng hỗ trợ của chúng tôi đang chờ để giúp bạn tại @FirefoxSupport trên Twitter và /r/firefox trên Reddit.

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

Firefox opens first suggested URLinstead of auto-completed URL

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

more options

Hello!

I couldn't find a solution, maybe because I wasn't using a proper naming.

When you start typing an URL in firebox URL-bar, suggestions appear below:

http://i.imgur.com/0f8o5ir.png

The problem's source is, auto-completion suggestion for the input field is different than the first page suggested below. I perfectly understand why algorithms for these two are different.

However the problem is that I often type one URL into the bar, press ENTER, and another URL opens! I finally managed to find circumstances for when it happens:

1. Type such character(s) to get an auto-completion suggestion different, than the first proposed page below (like on the given screenshot). 2. Highlight the first proposed page, by moving your mouse cursor over it. 3. Click on the URL-bar to confirm the suggestion. 4. At this point it should be clear what page you will open: http://i.imgur.com/s8YUT6k.png 5. Press ENTER. Another URL (the one highlighted) will open instead.

Also, if in p. 3. instead of clicking on the URL-bar you will press [RIGHT] key, the auto-completion (selected text) will be ignored and the 1st suggested link will be inserted instead.

I believe such output is not intuitive. Thanks to investigating the issue in order to find how to reproduce it, I understood the process and know how to avoid it - by not highlighting any suggestions. However you may want to fix it to avoid many frustrations of other users. In my opinion pressing the [RIGHT] key should complete the "selected" URL, and pressing [ENTER] should accept the URL typed, not the one highlighted, especially when the latter is hidden.

Hello! I couldn't find a solution, maybe because I wasn't using a proper naming. When you start typing an URL in firebox URL-bar, suggestions appear below: http://i.imgur.com/0f8o5ir.png The problem's source is, auto-completion suggestion for the input field is different than the first page suggested below. I perfectly understand why algorithms for these two are different. However the problem is that I often type one URL into the bar, press ENTER, and another URL opens! I finally managed to find circumstances for when it happens: 1. Type such character(s) to get an auto-completion suggestion different, than the first proposed page below (like on the given screenshot). 2. Highlight the first proposed page, by moving your mouse cursor over it. 3. Click on the URL-bar to confirm the suggestion. 4. At this point it should be clear what page you will open: http://i.imgur.com/s8YUT6k.png 5. Press ENTER. Another URL (the one highlighted) will open instead. Also, if in p. 3. instead of clicking on the URL-bar you will press [RIGHT] key, the auto-completion (selected text) will be ignored and the 1st suggested link will be inserted instead. I believe such output is not intuitive. Thanks to investigating the issue in order to find how to reproduce it, I understood the process and know how to avoid it - by not highlighting any suggestions. However you may want to fix it to avoid many frustrations of other users. In my opinion pressing the [RIGHT] key should complete the "selected" URL, and pressing [ENTER] should accept the URL typed, not the one highlighted, especially when the latter is hidden.

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

more options

hello Etherlord, thanks for bringing this up! this is a regression in firefox 31 and there's already a bug on file for this behaviour (please don't post in bug reports, but vote for the bug if you want to see it fixed): bug #1043584