Diorser wrote:I would not like to abuse... but it seems so easy to you.......
Then don't.
And while in some cases the solution is indeed quite simple, similar solutions can be more difficult than imagined.
Diorser wrote:How to make download open in a tab by default (when open by the system).
I'm afraid, that's one of the more difficult issues and not solvable with userChrome.js except with major hackery (which I'm not willing to even try).
dougeeebear wrote:to open in a new tab instead of a window, and I'm not having any luck with it.
AFAICT, you'll have to overwrite <code>BookmarkCommand.manageFolder</code> (
original code) to open a new tab instead - and then make sure that you somehow pass the argument to the tab (the argument is used
here). Good luck.
XerBlade wrote:Anyone know a way I can add a toolbar buttons to the ends of the tab bar (without using one of the extensions that adds small actual toolbars to the ends of it)?
Code: Select all
document.getAnonymousNodes(getBrowser().tabContainer)[0]
.appendChild(toolbarButton);
XerBlade wrote:And, while I'm at it, move already existing buttons there?
Just have <code>toolbarButton</code> in the snippet above point to an actual button (e.g. <code>var toolbarButton = document.getElementById("back-button");</code>). Further tweaking/styling will probably be necessary, though.
Diorser wrote:Only thing to improve for history manager: the Tab is not labelled "History Manager", but chrome://browser/content/history/history-panel.xul ...
Try the following instead of the original snippet:
Code: Select all
document.getElementById("viewHistorySidebar").setAttribute("oncommand", 'var tab = getBrowser().selectedTab = getBrowser().addTab("chrome://browser/content/history/history-panel.xul"); setTimeout(function() { tab.label = "History Manager"; }, 0);');
giuliastro wrote:Ok, then there is some sort of bug with 0.7 and Firefox 1.5.0.3 on Linux.
Do you get any errors in the JS console (having the hidden pref javascript.options.showInConsole set to true)? Make sure Firefox does have write access to the chrome directory. The userChrome.js code should actually be so simple as to not being able to contain bugs...
giuliastro wrote:Do you think there is some way to use userChrome to filter/parse mail text?
It should be possible to intercept the message before it is sent by getting into the compose window through the WindowHook snippet (see this thread's
first post) and there intercepting/modifying the <code>GenericSendMessage</code> method (see
MsgComposeCommands.js). Currently, writing a proper extension will require slightly less hackery, though.