Where is the button "history-panelmenu" defined?
I couldn't find it in "browser.xul".
I'd like to add a right-click function to the button. I can do that as follows:
var historyUndo = document.getElementById("history-panelmenu"); historyUndo.addEventListener("click", function(event) { if(event.button != 0) undoCloseTab(); }, false); historyUndo.setAttribute("context", "");
But I'd rather change the xul file.
Thank you.
Solution choisie
See:
- resource:///modules/CustomizableUI.jsm
- resource:///modules/CustomizableWidgets.jsm
Toutes les réponses (5)
Solution choisie
See:
- resource:///modules/CustomizableUI.jsm
- resource:///modules/CustomizableWidgets.jsm
Modifié le par cor-el
Thank you so much. I really appreciate it.
I've added the following 2 lines to "const CustomizableWidgets" in CustomizableWidgets.jsm:
context: "",
onClick: function(event) { if(event.button != 0) undoCloseTab(); }
This is the code after the change:
const CustomizableWidgets = [{
id: "history-panelmenu",
type: "view",
viewId: "PanelUI-history",
shortcutId: "key_gotoHistory",
tooltiptext: "history-panelmenu.tooltiptext2",
defaultArea: CustomizableUI.AREA_PANEL,
context: "",
onClick: function(event) { if(event.button != 0) undoCloseTab(); }
onViewShowing: function(aEvent) {
***
I re-zipped the files and replaced omni.ja, but it doesn't work. Any idea?
Modifié le par cor-el
undoCloseTab() without an index might not work.
Thanks again. It's kind of you.
Using "undoCloseTab()" in an extension works as expected.
Do you know if the "onClick" is correct? Should changes in JSM files apply without any further actions?
I've just erased some code in CustomizableWidgets.jsm, and it has no effect. It seems that modifying the file is not enough. What do you think?
I used -purgecaches.