Open espadrine opened 11 years ago
So here is my take on this: If lets say there are more than 15 entries, say 25, thus a scrollbar appears. Now the use of scrollbar is to be able to reach to every suggestion, even the 25th one. Now there are two ways to reach the overflowed entries :
In both of the cases, he will need more than 3-4 keystrokes to reach to the desired entry. Now if instead, we show only 15 entries, thus the last 10 are not shown, and he wants to reach to them, he can type one or two characters to have them visible.
Now lets us consider the case when the user does not know the property starting characters, or the whole property at all, in that case, it almost has the same effect on having or not having the last 10 entries visible. But if we show the entries by default, we might break the popup by the introduction of a scrollbar, which causes a lot of awful things :( . Thus I want to avoid a scrollbar as much as possible. Moreover, in most of the cases, the last entries are the _not_somuch required entries like __proto__
, toSource
, etc
If integrating a scrollbar is more work than it's worth, here's another option: tab'ing to the bottom goes beyond on the list. I do realize how cryptic that last sentence was, so here's ASCII art.
window.| | window.| | window.|
<Object> | Object | Object
Function | <Function> | Function
eval | eval | <eval>
window.| | window.|
Function | eval
eval | netscape
<netscape> | <Window>
In the default UI, it would be great to have the option of scrolling through all entries, instead of restraining to a fixed number of shown guesses. @scrapmac, what do you think?