Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

blazar (7356)

blazar
  (email not shown publicly)
http://blazar.perlmonk.org/
Yahoo! ID: bik.mido (Add User, Send Message)
Jabber: blazar@jabber.org

Journal of blazar (7356)

Monday November 13, 2006
12:01 PM

Speaking of FF 2.0

[ #31593 ]

This is not an extensive review, for I'm sure there better ones around. I appreciate the work that has been done on new features and on consolidating old ones, but I will concentrate on one of them only. First of all, however, a brief remark about the new "resume browsing section" feature: nice, but I would love not to have to test it so often! Also, it does restore windows, and tabs (I don't know downloads, although it is claimed to) but not text written in forms, well, at least not in textareas, and that can be annoying. However I'm aware that the frequent crashes may be due to my particular system, and I'm positive that any problem will be solved in the next minor releases.

Now, let's come to the main point that I want to discuss, which is, in view of my interest for interfaces, the new tabbed browsing system. Actually, I'm not really sure whether to consider it as an improvement...

Generally I'm a supporter of KISS all the time. In this case consider what we had before: any number of tabs displayed simultaneously, that could shrink arbitrarily. Now we have left and right arrows to scroll while viewing a limited number of them at once. Which scheme is simpler? I'm half hearted: with the previous one, one had an intuitive idea of how many were open, but indeed things could get quite messy. (I occasionally open 30 or more!) With the new one, things are certainly more ordered under any circumstance.

What I still consider not to be an improvement is the choice of having a close button per tab. First of all it makes the visual appearance heavier, notwithstanding the fact that it's shaded (depending on the chosen theme, I guess, but most will do, I also guess) in inactive tabs. Second, and more important, previously one used to have a single close button in a fixed position, now the position changes with the frame one is actually viewing. I suppose it's all a matter of getting used to any of these choices, but in any case I cosider the current one to be conceptually more complex while buying one nothing, and overloading each tag. I wish at least there were an option to choose between the old and the new behaviour.

Last, recently closed tabs in history are a great tool, of course!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • it does restore windows, and tabs […] but not text written in forms, well, at least not in textareas

    It doesn’t? It does for me! Maybe something is broken in your install? Maybe you want to try the Firefox version of reinstalling Windows: start over with a fresh profile. (Just copy over your cookies and bookmarks.) See if that helps.

    In this case consider what we had before: any number of tabs displayed simultaneously, that could shrink arbitrarily.

    Note, though, that the previous scheme

    • It doesn’t? It does for me! Maybe something is broken in your install? Maybe you want to try the Firefox version of reinstalling Windows: start over with a fresh profile. (Just copy over your cookies and bookmarks.) See if that helps.

      Well, that's not that much of a hassle after all. Should it crash when editing into a textarea, and fail to restore what I had written up to then, I will consider doing so...

      Note, though, that the previous scheme had a massive fault: tabs didn’t shrink endlessly

      --
      -- # This prints: Just another Perl hacker, seek DATA,15,0 and print q... ; __END__