Much obliged. Do you know if applying this hack will screw up future Firefox delta updates?
Not to my knowledge as yet. I say that because every update I make (which I do manually) I apply this hack so if anything changed I would see it immediately - I run DIFFs for my own personal interest. As you'll see from the date of my hack post I've been doing this for months now and have had no problems.
That seems unlikely to me, because the CRC of the file to be patched is checked before applying a partial update. The CRC is the same sort of thing as an MD5sum - a short digital signature that uniquely encodes the file contents - and it will change when you modify browser.jar (which itself changes quite often).
Full updates will just blow the existing browser.jar out of the water and should work fine.
Peter(6) wrote:2. do like e.g. Windows XL and add [<<][<] and [>][>>] buttons. I experimented with option 1, and it isn't too bad, I'd love to try option 2 and see how that looks/works
Option 2 is definitely more desirable and what I had in mind. Once the tabs extend too far, you would get the arrow buttons to navigate through them.
Preferably right away, there's nothing as bad as stuff jumping on any of your toolbars (the point when you need the arrows).So what if they eat 1/2 a tab of space all the time, it'll only mean you reach the point needing them after 6 i/o of 7 tabs, who cares
We would have to find out the best miniumum width for a tab after which the scrolling would be activated.
Additionally, it would be less pain if you could scroll by just hovering the << and >> and/or using mouse wheel when over tab bar.
Does not work as well as LastTab 1.5.1. With LastTab pressing Ctrl+Tab switched between the last two selected tabs, just like Alt+Tab in Windows. Also closing a tab does not get me back to the previously active tab.
Why not just add LastTab functionality into Firefox instead? Or at least make the LastTab functionality available as an option.
ByTor201 wrote:Here is a non-Windows specific program that shows exactly how I think the tabs should be handled: Xchat. For example:
I think that arrows should be located on their respective sides (i.e. far right and far left), not both on the right. The latter is used in similar cases in many applications and it's usually a poor solution in terms of usability, esp. when you want to scroll to the left:
- it's much less intuitive
- it kills the idea of scrolling by hovering the edge of tab box
- you have to first move your mouse to the far right and then, when the tab you were scrolling to shows up, to the far left to click it.
Better to be both on one side becaue if you over scroll then why should you have to move your mouse all the way to the left to hit the arrow once? Both sould be on same side, I vote the right.
on another note just seen a commercial on tv while typing this for dentalplans.com and its using firefox
Last edited by supernova_00 on January 22nd, 2006, 11:45 am, edited 1 time in total.
At the moment, I don't really have the time to work on TBP to fix any breakage caused by the XBL changes to the tabbrowser element. If anyone is willing to fix the breakage in a portable fashion (i.e. the code works on the MOZILLA_1_8_BRANCH as well as the trunk), I'll take the changes after 1.3.0 is released.
Proud user of teh Fox of Fire Registered Linux User #289618
supernova_00 wrote:Better to be both on one side becaue if you over scroll then why should you have to move your mouse all the way to the left to hit the arrow once? Both sould be on same side, I vote the right.
on another note just seen a commercial on tv while typing this for dentalplans.com and its using firefox
lol i saw on foxnews a while back ppl on news using firrefox
I can't code it but maybe someone can create a patch using the autorepeatbutton which is what the bookmarks menu uses to scroll when there are too many bookmarks for the screen. Here is lxr query
supernova_00 wrote:Better to be both on one side becaue if you over scroll then why should you have to move your mouse all the way to the left to hit the arrow once? Both sould be on same side, I vote the right.
The same happens when you want to scroll to the left and have to move your mouse all the way to the left to click the tab after scrolling. But your case is hit only by mistake, whereas mine every single time you scroll.
To over scroll you'd have to keep scrolling while the desired tab moves all the way across the screen and then disappears on the opposite side. How often would that happen?
This is the solution with menus and it proved to be good. You don't complain about it in menus, do you? It's also about consistency.
supernova_00 wrote:Better to be both on one side becaue if you over scroll then why should you have to move your mouse all the way to the left to hit the arrow once? Both sould be on same side, I vote the right.
Wrong for (at least) 3 reasons:
1. it's not ergonomic (imagine you would have that with the up/down arrows on bookmarks)
2. people with the slightest visual disability would have massive problems if they were at one side
3. it's asymetric and therefore not logical
<a href="http://imageshack.us"><img src="http://img492.imageshack.us/img492/9833/scrolltabs5qr.png" border="0" width="439" alt="Image Hosted by ImageShack.us" /></a>
How about this? The reasons why IMHO this is more usable is because with one click on the arrows (up/down) you will be exposed to 10-12 tabs (depending on mintabwidth)...instead of just one tab with left/right arrows.
The maximum number of visible tab-bars can be limited to 2 (or more through hidden options as per user's choice)...
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
