搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Add a buffer for keyinputs that will be used when an input field gets autofocused

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 RikS

more options

When I go to a search website, for instance google, and start typing too early, the first part of what I am typing will not be in the input field. As example. Say I have a bookmark that goes to google. I click it and start typing "Volcano eruption" it is highly likely that I will get something like "ano eruption", because I started typing too early.

It would be nice if firefox would keep a buffer of typed characters while a page is loading, so that these characters could be automatically filled in to any input field that gets auto-focussed by the website. That way, in the example before, the letters "Volc" would be buffered and automatically filled into the input field, so that in the end it will correctly contain the full "Volcano eruption".

When I go to a search website, for instance google, and start typing too early, the first part of what I am typing will not be in the input field. As example. Say I have a bookmark that goes to google. I click it and start typing "Volcano eruption" it is highly likely that I will get something like "ano eruption", because I started typing too early. It would be nice if firefox would keep a buffer of typed characters while a page is loading, so that these characters could be automatically filled in to any input field that gets auto-focussed by the website. That way, in the example before, the letters "Volc" would be buffered and automatically filled into the input field, so that in the end it will correctly contain the full "Volcano eruption".

所有回覆 (2)

more options

That is coming from Google not FF otherwise you need to check your settings in something like Prediction that Google chrome has or a settings is set wrong.

more options

This has nothing to do with google chrome. I was talking about the search engine and any other (bing, yahoo, you name it) would have the same issue. Also it is something that the website cant fix, because to my knowledge a website cant record keystrokes before even the html and js files are loaded. This is a feature request that really needs to be implemented in the browser itself.