{"id":4516,"date":"2011-02-27T01:33:00","date_gmt":"2011-02-27T09:33:00","guid":{"rendered":"http:\/\/www.oeconomist.com\/blogs\/daniel\/?p=4516"},"modified":"2011-02-27T22:15:51","modified_gmt":"2011-02-28T06:15:51","slug":"the-red-death","status":"publish","type":"post","link":"https:\/\/www.oeconomist.com\/blogs\/daniel\/?p=4516","title":{"rendered":"The Red Death"},"content":{"rendered":"<p>Uhm, Firefox programmers?  I have a question for you: What does this thing <img loading=\"lazy\" decoding=\"async\" src=\"wp-content\/uploads\/2011\/02\/button_150x150j.png\" alt=\"[enlarged image of red button with central 'x' from Navigation Toolbar]\" width=\"150\" height=\"150\" style=\"border: 0 ; display: block ; margin-top: 1em ; margin-bottom: 1em ; margin-left: auto ; margin-right: auto ;\" \/> actually <em>mean?<\/em>  You know, that red button with the central white <q>x<\/q> on the Navigation Toolbar. <img loading=\"lazy\" decoding=\"async\" src=\"wp-content\/uploads\/2011\/02\/button_insitu.png\" alt=\"[image of red button on Navigation Toolbar]\" width=\"300\" height=\"138\" style=\"border: 0 ; display: block ; margin-top: 1em ; margin-bottom: 1em ; margin-left: auto ; margin-right: auto ;\" \/>  What's s'posed to happen when I click on it?<\/p> <p>Let me explain my question.  Traditionally, browsers gave me something like <em>this<\/em> <img loading=\"lazy\" decoding=\"async\" src=\"wp-content\/uploads\/2011\/02\/stop_150x150.png\" alt=\"[image of hexagon]\" width=\"150\" height=\"150\" style=\"border: 0 ; display: block ; margin-top: 1em ; margin-bottom: 1em ; margin-left: auto ; margin-right: auto ;\" \/> It looks a lot like a <em>stop sign<\/em>, and clicking on it was a lot like stepping on a <em>brake<\/em>.  The browser <em>stopped<\/em> what it was doing.  That's <em>not<\/em> exactly what happens when I click on your little red-circle-with-the-eks.  Now, it's as if my brakes have been redesigned <em>by a passive-aggressive sociopath<\/em>.   Metaphorically speaking, the car will no longer stop <em>before<\/em> it goes into the intersection; instead, it will stop either on the other side or just in the intersection.<\/p> <p>Really, I mean, when I'd discover that a site was trying to send me some big-ass graphic, I would use the friendly stop-sign button, and it would stop the loading of that thing.  The new red button says <q>Just a minute; let me finish loading this big-ass graphic.<\/q>  Or I'd click on a link, and things would churn and churn, so I'd decide to bail.  With the stop-sign button, the browser just stopped, leaving me at the prior page on which the link was; with the new red button, it goes to a blank screen (and then, to back-up, Firefox demands that the server of the previous page be re-sent everything to reload the page from scratch, which might not even be directly possible).<\/p> <p>Anyway, I'd like either to get the functionality associated with the old button restored, or at least some honest revelation of the functionality associated with this new button.  It seems, well, <em>evil<\/em>.<\/p> <p><abbr title=\"thanks\">TNX<\/abbr>.<\/p>","protected":false},"excerpt":{"rendered":"Uhm, Firefox programmers? I have a question for you: What does this thing actually mean? You know, that red button with the central white x on the Navigation Toolbar. What's s'posed to happen when I click on it? Let me explain my question. Traditionally, browsers gave me something like this It looks a lot like [&hellip;]","protected":false},"author":1,"featured_media":4517,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[6,69,4],"tags":[957,253,956,250],"class_list":["post-4516","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-commentary","category-information-technology","category-public","tag-browsers","tag-firefox","tag-mozilla","tag-programming"],"_links":{"self":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/posts\/4516","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4516"}],"version-history":[{"count":0,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/posts\/4516\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/media\/4517"}],"wp:attachment":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4516"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4516"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4516"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}