4 ms·
I know that, because that's what I do. But my point is, I shouldn't have to know how to 'hack' around the browser just to use a textbox. That's really inferior
by silverbax88 9y ago
I know that, because that's what I do. But my point is, I shouldn't have to know how to 'hack' around the browser just to use a textbox. That's really inferior UX design. I shouldn't even be thinking about any of that, I should be thinking about what the Google results are, not how to use Google.
- manigandham 9y agoWhat are you hacking around? Why not just use the address bar all the time?
- shitgoose 9y agothen why putting an input area in the middle of the page with inviting prompt "search google or type url"? simple act of entering search terms and pressing Enter button - instead turns into a mental game of "if it is a brand new search, then search terms will appear in url bar no matter where i type them; when search results come, my search terms will be copied to the input box on the page and later can be edited there". sorry, this is just plain stupid. sounds like an executive design, no normal developer would come up with this crap.
- silverbax88 9y agoThen why does Google have a textbox on the app? Why not just put a blank page as their front page? And why does the textbox only suddenly move your input from a web app element to a browser element in only this one instance? What solution does this solve for me, the user, to have to determine that in this one instance, the textbox can't be used, but on literally every other application out of millions of web applications, text boxes work correctly?