{"id":384,"date":"2011-01-31T17:04:05","date_gmt":"2011-01-31T06:04:05","guid":{"rendered":"http:\/\/xhva.net\/log\/?p=384"},"modified":"2011-01-31T17:31:03","modified_gmt":"2011-01-31T06:31:03","slug":"removing-the-last-updated-text-from-firefox-4s-addon-manager","status":"publish","type":"post","link":"https:\/\/xhva.net\/log\/2011\/01\/removing-the-last-updated-text-from-firefox-4s-addon-manager\/","title":{"rendered":"Removing the \u2018last updated\u2019 text from Firefox 4\u2019s addon manager"},"content":{"rendered":"<p><a href=\"http:\/\/jboriss.wordpress.com\/2011\/01\/26\/simplifying-and-polishing-the-add-ons-managers-list-view\/\">Jen\u00adny Boriss writes<\/a>:<\/p>\n<blockquote>\n<p>The intend\u00aded pur\u00adpose of the add-on manager\u2019s list view is to give a brief overview of the users\u2019 add-ons and to pro\u00advide only the min\u00adi\u00admal, most used infor\u00adma\u00adtion and functionality.<\/p>\n<\/blockquote>\n<p>I don\u2019t think a small chunk of text on each addon entry is caus\u00ading the man\u00adag\u00ader to be aes\u00adthet\u00adi\u00adcal\u00adly busy. The absurd amount of white\u00adspace and con\u00adfus\u00ading visu\u00adal struc\u00adture is actu\u00adal\u00adly respon\u00adsi\u00adble for&nbsp;that.<\/p>\n<p><a href=\"http:\/\/xhva.net\/log\/wp-content\/uploads\/2011\/01\/addons-huge.png\"><img decoding=\"async\" loading=\"lazy\" src=\"http:\/\/xhva.net\/log\/wp-content\/uploads\/2011\/01\/addons-huge-300x155.png\" alt title=\"addons-huge\" width=\"300\" height=\"155\" class=\"alignleft size-medium wp-image-362\" srcset=\"https:\/\/xhva.net\/log\/wp-content\/uploads\/2011\/01\/addons-huge-300x155.png 300w, https:\/\/xhva.net\/log\/wp-content\/uploads\/2011\/01\/addons-huge-1024x529.png 1024w, https:\/\/xhva.net\/log\/wp-content\/uploads\/2011\/01\/addons-huge.png 1680w\" sizes=\"(max-width: 300px) 100vw, 300px\"><\/a><\/p>\n<p>Some addi\u00adtion\u00adal com\u00adments about the addon man\u00adag\u00ader inter\u00adface can be found in <a href=\"http:\/\/xhva.net\/log\/2011\/01\/questions-to-the-firefox-4-ui-team\/\">a pre\u00advi\u00adous post about the Fire\u00adfox 4 UI<\/a>.<\/p>\n<blockquote>\n<p>Some advanced users use the last updat\u00aded date as a diag\u00adnos\u00adtic tool to iden\u00adti\u00adfy which add-on updates may be caus\u00ading a recent prob\u00adlem in Fire\u00adfox.  How\u00adev\u00ader, the date makes a very poor diag\u00adnos\u00adtic tool. One rea\u00adson is that the date does not give any infor\u00adma\u00adtion about the size nor scope of the update, and thus can only be used for diag\u00adno\u00adsis by dis\u00adabling one add-on at a time to iso\u00adlate a prob\u00adlem.  In many cas\u00ades, a prob\u00adlem in Fire\u00adfox caused by an add-on are instant\u00adly iden\u00adti\u00adfi\u00adable as being caused by a par\u00adtic\u00adu\u00adlar add-on.<\/p>\n<\/blockquote>\n<p>This has not been my expe\u00adri\u00adence. Dis\u00adabling the last updat\u00aded addon has been a suc\u00adcess\u00adful tech\u00adnique for me in at least two cas\u00ades. For exam\u00adple, towards the end of last year half of my tabs dis\u00adap\u00adpeared with one mid\u00addle-click. I have a few tab-relat\u00aded addons installed so a few were sus\u00adpect. Luck\u00adi\u00adly I remem\u00adbered which one had updat\u00aded last (around week pri\u00ador to the bug sur\u00adfac\u00ading so dra\u00admat\u00adi\u00adcal\u00adly) so I down\u00adgrad\u00aded the <a href=\"http:\/\/piro.sakura.ne.jp\/xul\/_treestyletab.html.en\">Tree-style Tabs<\/a> addon and things went back to nor\u00admal. This is a case where sort\u00ading by last update date is very use\u00adful. (Or maybe it\u2019s because I\u2019m an advanced user who can <a href=\"http:\/\/www.youtube.com\/watch?v=1uONg5voLxo\">tie his own shoelaces with\u00adout a video demon\u00adstra\u00adtion on Youtube<\/a>).<\/p>\n<p>What would be ide\u00adal for sit\u00adu\u00ada\u00adtions like this is for recent\u00adly-updat\u00aded addons to have a \u2018down\u00adgrade\u2019 or \u2018down-date\u2019 (for want of a bet\u00adter term) option avail\u00adable to the user should some\u00adthing appear wrong with the addon that can\u2019t be explained through error logs or crash reports. This fea\u00adture also com\u00adpen\u00adsates for users who update an addon (or have it updat\u00aded auto\u00admat\u00adi\u00adcal\u00adly) only to dis\u00adcov\u00ader a key fea\u00adture that they used has been changed or removed.<\/p>\n<blockquote>\n<p>Even in the rare case where a prob\u00adlem sud\u00adden\u00adly appears in Fire\u00adfox, the chances of it being from an add-on update are not large.  A prob\u00adlem could be caused by any num\u00adber of online events, which is why Fire\u00adfox pro\u00advides tools such as the Error Con\u00adsole and about:crashes to help diag\u00adnose&nbsp;them.<\/p>\n<\/blockquote>\n<p>The con\u00adsole out\u00adput and about:crashes would not have helped for the case above as it was a log\u00adic error in the addon, not a syn\u00adtax&nbsp;error.<\/p>\n<blockquote>\n<p>And, even if we were to give fuller infor\u00adma\u00adtion about updates in the add-ons man\u00adag\u00ader and make it into a bet\u00adter diag\u00adnos\u00adtic tool, why should this tool be so far removed from oth\u00ader diag\u00adnos\u00adtic tools?  How could a new user fig\u00adure out that, to access diag\u00adnos\u00adtic tools relat\u00aded to add-ons, they should go to the add-ons man\u00adag\u00ader rather than a more com\u00adpre\u00adhen\u00adsive diag\u00adnos\u00adtic tool?  It would be wild\u00adly inef\u00adfi\u00adcient to apply this else\u00adwhere in Fire\u00adfox by plac\u00ading diag\u00adnos\u00adtic tools only on the inter\u00adface ele\u00adments they relate to.<\/p>\n<\/blockquote>\n<p>No one asked for diag\u00adnos\u00adtic tools to be splayed through\u00adout the inter\u00adface, so I\u2019m not sure where that came from. I cer\u00adtain\u00adly don\u2019t want the dash\u00adboard of my car look like a 747 cock\u00adpit but I would like to be giv\u00aden a hint about the oil lev\u00adel since that <em>changes over time while I\u2019m not look\u00ading<\/em>.<\/p>\n<p>If I was a user with a few addons that affect say, tabs, and the tab bar start\u00aded act\u00ading funky, I\u2019d think about what change could have caused it. Did I fid\u00addle with any set\u00adtings? No. Did the brows\u00ader update in the last week? No. Did those tab addons update? Hmm, I remem\u00adber see\u00ading some\u00adthing about that. How do I check stuff about addons? Oh, the <em>addon man\u00adag\u00ader<\/em>.<\/p>\n<p>I think strip\u00adping out poten\u00adtial\u00adly use\u00adful diag\u00adnos\u00adtic infor\u00adma\u00adtion for pure\u00adly aes\u00adthet\u00adic rea\u00adsons is the wrong choice. Con\u00adsid\u00ader the dif\u00adfer\u00adence in time and com\u00adplex\u00adi\u00adty if I want to find the most recent\u00adly updat\u00aded addon for the sce\u00adnario&nbsp;above:<\/p>\n<ul>\n<li><strong>With sortable dates<\/strong>: click \u2018last updat\u00aded\u2019 and look at the top of the&nbsp;list.<\/li>\n<li><strong>With\u00adout sortable dates<\/strong>: dou\u00adble click an addon on the list and find the \u2018last updat\u00aded\u2019 field. This will be be in a dif\u00adfer\u00adent screen posi\u00adtion depend\u00ading on the descrip\u00adtive text sup\u00adplied by the addon author. Is the update date the clos\u00adest to now that you\u2019ve found so far? Repeat until you\u2019ve checked all addons.<\/li>\n<\/ul>\n<blockquote>\n<p>What we should do is add diag\u00adnos\u00adtic tools about add-ons to com\u00adpre\u00adhen\u00adsive tools such as about:support.  Then, we could  pro\u00advide expert users the infor\u00adma\u00adtion they want in a bet\u00adter for\u00admat while keep\u00ading one-off diag\u00adno\u00adsis away from list view in the add-ons manager.<\/p>\n<\/blockquote>\n<p>Well, yeah, that\u2019d be great. When is that sched\u00aduled to be includ\u00aded? In the mean\u00adtime, however\u2026<\/p>\n<blockquote>\n<p>The intend\u00aded pur\u00adpose of auto\u00admat\u00adic updates is to remove updat\u00ading from the list of items the user has to care about and remem\u00adber.  By expos\u00ading the updat\u00aded date in list view, Fire\u00adfox insin\u00adu\u00adates both that the updat\u00aded date is very impor\u00adtant that this is a process the user should manage.<\/p>\n<\/blockquote>\n<p>Please don\u2019t do that. You\u2019re assum\u00ading that the addon review process is per\u00adfect. If it was then the bro\u00adken Tree-style Tab update would\u00adn\u2019t have got\u00adten through and remained live for 2+&nbsp;weeks.<\/p>\n<p>I also dis\u00adagree that show\u00ading an infor\u00adma\u00adtion update date is insin\u00adu\u00adat\u00ading that the user is respon\u00adsi\u00adble for it. If Fire\u00adfox suc\u00adcess\u00adful\u00adly com\u00admu\u00adni\u00adcates that addons are auto-updat\u00aded then you have noth\u00ading to wor\u00adry&nbsp;about.<\/p>\n<blockquote>\n<p>Actu\u00adal\u00adly, the actu\u00adal rea\u00adson sort\u00ading and the last updat\u00aded date were ini\u00adtial\u00adly pro\u00adposed in the add-ons man\u00adag\u00ader design was to give users the abil\u00adi\u00adty to sort their add-ons by per\u00adfor\u00admance, not updat\u00aded date. [\u2026] How\u00adev\u00ader, the abil\u00adi\u00adty to rank an add-on\u2019s per\u00adfor\u00admance is going to be a part of FIre\u00adfox after the 4.0 release, mak\u00ading the remain\u00ading sort\u00ading cat\u00ade\u00adgories (alpha\u00adbet\u00adic and updat\u00aded date) much less useful.<\/p>\n<\/blockquote>\n<p>Are you say\u00ading that sort\u00ading by name &amp; date will be back when per\u00adfor\u00admance grad\u00ading is pos\u00adsi\u00adble? If so then this change and dis\u00adcus\u00adsion are a waste of&nbsp;time.<\/p>\n<p>Edit: from the com\u00adments under\u00adneath the article:<\/p>\n<blockquote>\n<p>Pref\u00ader\u00adences will be in detailed view also. So, it can be accessed by click\u00ading the name of an add-on once. It\u2019s basi\u00adcal\u00adly the same rea\u00adson\u00ading \u2013 that this is func\u00adtion\u00adal\u00adi\u00adty that isn\u2019t basic, scannable, most used-enough for list view, but is per\u00adfect for detail view. Detail view is essen\u00adtial\u00adly for more com\u00adplex inter\u00adac\u00adtions with add-ons, while list-view is for over\u00adall sum\u00adma\u00adry. Pref\u00ader\u00adences is an exam\u00adple of a more com\u00adplex interaction.<\/p>\n<\/blockquote>\n<p>This sounds real\u00adly non-intu\u00aditive and goes against the <a href=\"http:\/\/en.wikipedia.org\/wiki\/Principle_of_least_astonishment\">prin\u00adci\u00adple of least sur\u00adprise<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Jen\u00adny Boriss writes: The intend\u00aded pur\u00adpose of the add-on manager\u2019s list view is to give a brief overview of the users\u2019 add-ons and to pro\u00advide only the min\u00adi\u00admal, most used infor\u00adma\u00adtion and func\u00adtion\u00adal\u00adi\u00adty. I don\u2019t think a small chunk of text on each addon entry is caus\u00ading the man\u00adag\u00ader to be aes\u00adthet\u00adi\u00adcal\u00adly busy. The absurd&nbsp;[\u2026]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"ngg_post_thumbnail":0},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/posts\/384"}],"collection":[{"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/comments?post=384"}],"version-history":[{"count":12,"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/posts\/384\/revisions"}],"predecessor-version":[{"id":391,"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/posts\/384\/revisions\/391"}],"wp:attachment":[{"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/media?parent=384"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/categories?post=384"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xhva.net\/log\/wp-json\/wp\/v2\/tags?post=384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}