2 ms·
UI crudeness is one thing. What I wonder about is whether those links generate HTTP GET-requests. Links do so by default. If so, just need internal web spider
by vardump 9y ago
UI crudeness is one thing.
What I wonder about is whether those links generate HTTP GET-requests. Links do so by default.
If so, just need internal web spider or overzealous web browser prefetcher, and one day Hawaii might have a lot of false alerts going on...
GET-requests are not supposed to have side effects, like alerting a whole state.
When you have side effects, HTTP verb should be something else, like POST.
Of course, it's possible there's Javascript handler behind those links that generates a HTTP POST request. Overall appearance of the page does suggest otherwise.
I wonder how the confirmation page (if any) behaves and looks like...
- bfrydl 9y agoYou're assuming a lot here. This might not even be an HTML page. It used to be fairly common in Windows UIs to have underlined blue clickable text in native applications.
- vardump 9y agoWell, all I know it looks like an unstyled web page. We can just guess indeed. Oh, and their display mode is set incorrectly. It's clearly non-native resolution (blurry text, bilinear "zooming" performed by the display, while individual pixels are in sharp focus) and wrong aspect ratio (the font appears too wide). Perhaps 1024x768 on a display with 1920x1080 native resolution. Or something similar.
- ChiliConKanye 9y agoIf you're referring to "HTMLHelp" help applications they actually were HTML pages, under native chrome. If you can think of any other usages in non-browser UIs where links where used to navigate would love to see them for nostalgia's sake.