I suspected them too, but i disabled them and the problem persisted...

note the d on the end of Session Saver 0.2d... This is a total rewrite by the same person who makes adblock...

Something else worth bringing up... if you have a slow connection, or a page which is really slow loading, and hasn't added any content to the window yet, using Ctrl-Tab, you can switch TO the tab, but not AWAY... (this is standard firebird behaviour, it happens with/without any extensions) However, using the scrollwheel on the tabs with this extension (also TBE) it allows you to scroll over and across the same tabs standard keyboard shortcuts struggled over... I want to get to the bottom of this, as it really ticks me off (this stalling on unloaded tabs buisness)

(Edited SS version to be correct )

Last edited by TychoQuad on January 23rd, 2004, 6:09 am, edited 1 time in total.

Frease: Sorry about that, I am using d as well... I went back and edited my posts

dorando: Thanks for taking the time to hunt down my stupid little bug... It would be the extension I would least expect, wouldn't it?

Anyway, I still think it is odd that I can scroll through loading tabs with the wheel, but not with the keyboard, and when doing so with the wheel, I don't experience any problems whatsoever... I always assumed scrolling on the tabbar just invoked the keyboard shortcuts in these types of extensions, but it doesn't appear so. Regardless of whether the conflict between TBX and miniT is sorted out or not, I think the Ctrl-Tab and Ctrl-Shift-Tab keycombos should be changed to do the same function as the mousewheel over the tabs. (if not just in this extension, why not the core?) That would also eliminate my risk of crash which is also assosiated with the dodgy keyboard shortcuts: http://forums.mozillazine.org/viewtopic.php?t=47220

TychoQuad wrote:Thanks for taking the time to hunt down my stupid little bug... It would be the extension I would least expect, wouldn't it?

Toolbar Enhancements changes the binding for "tabbox" which seems to cause this problem if the tabbrowser was accessed before (even without changing anything).

Until I've time to think about a fix you can open 'chrome/overlayinfo/browser/content/overlays.rdf' in your profile and move '<RDF:li>chrome://minit/content/minit.xul</RDF:li>' above '<RDF:li>chrome://toolbarext/content/</RDF:li>'. That should hopefully work.

TychoQuad wrote:I think the Ctrl-Tab and Ctrl-Shift-Tab keycombos should be changed to do the same function as the mousewheel over the tabs.

They already use the same functions, the problem is likely that the tabbox doesn't receive keyboard event until the tabbrowser got any content.

dorando wrote:Until I've time to think about a fix you can open 'chrome/overlayinfo/browser/content/overlays.rdf' in your profile and move '<RDF:li>chrome://minit/content/minit.xul</RDF:li>' above '<RDF:li>chrome://toolbarext/content/</RDF:li>'. That should hopefully work.

Thanks, I'll give that a try.

They already use the same functions, the problem is likely that the tabbox doesn't receive keyboard event until the tabbrowser got any content.

Is it possible for you to change this? I'm guessing the crash is caused by me trying to switch tabs at the same time content is loaded... Perhaps you could fool tabs into thinking they always have content when they just have a placeholder for content when it arrives?

1) docShell.allow* attributes can be changed via tab context menu.2) Tabs can be switched by turning the mousewheel on the tab bar.3) Bookmarks are opened in background if browser.tabs.loadInBackground is set to true.4) New tabs can be opened by double clicking on any tab.5) Tabs can be dragged. If dropped within the tab bar the tabs will be reordered, otherwise only the url is dropped as text/x-moz-url, text/html, or text/unicode.

Notes:Only Mozilla Firebird.Only profile installation.No configurations.Dragging tabs to the tab bar of another window does cause problems.Likely conflicts with TBE, but you wouldn't need this anyway in that case.

Changes:0.7.0.3 - miniT should now be fully initialized before Session Saver restores the session.0.7.0.2 - tabs are now also draggable as text/x-moz-url and text/html.0.7.0.1 - miniT used an object to read the prefs only available in pre 2002-09-18 builds or in Optimoz and Quicknote.

rue wrote:If you bind the tabbrowser to your own xbl-binding, you can execute your modifications before anything else happens[...]

Thanks, but one of the primary design goals for me was to archive these functions without XBL Bindings (might be an idiotic idea, tough).

My current test version (not uploaded) should hopefully be initialized after all bindings (which was the problem miniT had with Toolbar Enhancements), but before Session Saver (both original and yours).

Oh. For some reason I thought you intended yours to be standalone -- unmixed with other tabbrowser-enhancements.
.
I guess perpetual "compatibility maintenance" is assumed.
.
Btw, you could listen for a known "onload" event -- perhaps the tabbrowser's. That would ensure all bindings have completed. In a similar vein, you could wait for the window's "onload" and also modify any existing tabs as necessary (per SessionSaver).

Thanks again, but as said I already had a working approach (0.7.0.4), and another one was in preparation (0.7.0.5). Also I'm aware of other possible approaches if these cause problems.

---

New version up (actually two and actually yesterday): 0.7.0.4 and 0.7.0.5
0.7.0.4 should be initialized at the correct time, while it shouldn't matter for 0.7.0.5 in which order everything will be initialized. Also 0.7.0.5 should behave slightly better.

4711 pointed out to me that apparently on linux-gtk2+xft the DOMMouseScroll event will not be dispatched to the tab bar, but to the toolbar instead...
Instead of adding/removing the event handler on mouseover/mouseout, the event handler is now attached to the toolbar on linux since it doesn't seem to interfere with something else. Say if this is annoying and I'll modify it to only work on the tab bar.