designoir

Comments / show all

257. Nathan Tuggy wrote on November 6, 2008 01:28 AM GMT (reply):
     I’d love it if you could update the code to check for session resumes and do something sensible to all resumed tab ages: either a) set age to 0; b) remember age from last time; c) set age to maximum (e.g., color all tabs as old as possible); d) set age to some extension of previous age plus time Firefox closed (e.g., viewed tab 3 minutes ago when closed Firefox, left Firefox closed for 10 minutes, reopened, show tab as the equivalent of 13 minutes old).
     
     Of these, d) is perhaps the best, but also a bit unintuitive and (of course) hard to program. a) is my personal favorite.
     
     In any case, something should be done about session resume handling: I think half of the bugs come from this problem (or the English-language bugs, at all odds; no can read others).
258. relou_2000 wrote on November 30, 2008 02:30 AM GMT (reply):
     Please make it work with Anycolor extension. ( https://addons.mozilla.org/fr/firefox/addon/6991 )
     Thanks
259. penubag wrote on December 8, 2008 08:05 AM GMT (reply):
     Please, please make aging tabs compatible with FlagTab’s colors. The color from flagtabs disappears after a while. I’d love to keep aging tabs so please fix. Thank you very much.
260. karen cheatham wrote on December 12, 2008 05:05 PM GMT (reply):
     It doesn’t seem to work properly with Aeon Colors.
261. 4SD wrote on February 23, 2009 11:20 AM GMT (reply):
     Is it possible to make that plugin compatible with the theme Office 2007 Black?
262. IDEA wrote on April 14, 2009 06:19 AM BST (reply):
     add in that the faded tab(s) shrink (and other non faded ones expand) and you really really really really have something awesome ;) Something that should be default in firefox ;)
263. tomato wrote on June 9, 2009 12:26 PM BST (reply):
     Can you recommend a Firefox theme that will work with Aging Tabs on Mac OS X? How should I configure Preferences with that theme?
     
     I have tried the default theme (and a few others) with minimal extensions and it didn’t seem to work properly.
     
     Thanks.
264. Dran wrote on June 15, 2009 10:28 PM BST (reply):
     Two ideas:
     
     Often when I close a tab I visit another tab accidentally which I did not mean to visit. If I am only at that tab for a moment it should not mark it as recently visited.
     
     Secondly, there could be an option as to whether a tab is marked as recent or very old when it first appears. A tab opened but never viewed is very new but never visited, so users could have the option.
265. tomato wrote on June 19, 2009 03:24 AM BST (reply):
     I posted comment 263 where I could not make Aging Tabs work with Firefox on Mac OS X.
     
     I can now say I find Aging Tabs works really well with the Noia 2.0 eXtreme theme and custom aging colours enabled in Preferences, and even with Colourful Tabs enabled. (Works with some others too, but Noia is what I tested and liked).
     
     Thanks for a great extension!
266. Busty wrote on July 4, 2009 04:26 PM BST (reply):
     Bug report:
     With TabMix Plus and Aging Tabs enabled, Firefox’ 3.5 “New Tab” button is on the left instead on the right.
267. neolith wrote on July 8, 2009 10:55 AM BST (reply):
     I can’t seem to get custom colors to work with FF3.5.
268. Troy wrote on August 3, 2009 07:04 AM BST (reply):
     I can’t seem to get it to work with Midnightfoxy (2.090608).
     
     I’m using Firefox 3.5.1
269. Hubird wrote on August 6, 2009 08:50 AM BST (reply):
     Any chance of aging tabs being made compatible with Thunderbird 3 BETA 3 and up ?
270. Martin Jessen wrote on August 8, 2009 07:27 AM BST (reply):
     First of all, YOU CANNOT FIND THIS EXTENSION IN THE ADDONS SEARCH USING THE KEYWORD aging. AWESOME!!!
     
     You should add variable delay aging of tabs. That is, instead of aging each tab statically by a static X seconds, it should in fact age by X seconds the first time, age by Y seconds the next time, and then age by Z seconds the next time it should be aging. Where X < Y < Z
     
     This would age the tab fastest when it matters most (IE: When you are on the computer and browsing around actively), and least when it matters least (When you leave Firefox running overnight and come back). What happens right now is that I come back the next day and find all my tabs are BLACK (Thats the color I use to age) with no indication as to what is newest or oldest. I suppose I can increase my delay in seconds, but I find that my setting works good for short term browsing, but not long term.
     
     Either you should do this, or you should include some kind of exception for idle time (where NO browsing is occurring) where aging happens less and less frequently as idle time increases
     
     Basically I want the tabs to age initially fast, and less at later times, so some semblance of aging is still available if I return to Firefox the next day. Either provide dynamically adjusting aging times or use some idle time method to deliver!!
271. dwight wrote on August 24, 2009 10:15 AM BST (reply):
     aging tabs make my firefox slow, but i like the highlighting feature. pls. add an option to disable the aging tabs.
272. itsamutiny wrote on August 27, 2009 08:24 AM BST (reply):
     aging tabs doesn’t work with the following theme: https://addons.mozilla.org/en-US/firefox/addon/10288
273. metdivo wrote on August 29, 2009 04:53 PM BST (reply):
     Love the extension. With Themes Aeon Big/Jumbo, custom highlighted tab color does not work--stays light blue. You can change the highlighted text. Thanks.
274. tuggyne wrote on October 27, 2009 05:32 PM GMT (reply):
     Currently, 0.7.1 doesn’t properly handle the first tab in a restored session: the first tab appears to be brand-new every time I open a restored session, even if it had completely aged in the saved session.
275. Peter wrote on January 26, 2010 02:11 PM GMT (reply):
     Please make compatible with ColourfulTabs
276. X wrote on February 21, 2010 03:14 PM GMT (reply):
     Love the extension. Having a compatibility problem with FF v3.5.8.
     
     Any ideas?

Post a Comment