Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Kjo rrjedhë është arkivuar. Ju lutemi, bëni një pyetje të re, nëse keni nevojë për ndihmë.

How do I hook in to the "New Tab" page UI for the add-on I am writing?

  • 1 përgjigje
  • 1 e ka hasur këtë problem
  • 12 parje
  • Përgjigjja më e re nga Kevin

undo.close
undo.close
more options

I am writing an add-on called Undo Close, for Firefox Mobile. It allows the user to reopen recently closed tabs.

Currently, I provide an "Undo Close" button in the main menu (using the NativeWindow API). However, the ideal location for this button is in the BrowserTab UI. As far as I know, there is no JS-API for the native widgets located therein. How can I add my button to the UI, possibly using ctypes?

If interested, I can supply a link to my add-on in AMO.

I am writing an add-on called Undo Close, for Firefox Mobile. It allows the user to reopen recently closed tabs. Currently, I provide an "Undo Close" button in the main menu (using the NativeWindow API). However, the ideal location for this button is in the BrowserTab UI. As far as I know, there is no JS-API for the native widgets located therein. How can I add my button to the UI, possibly using ctypes? If interested, I can supply a link to my add-on in AMO.

Krejt Përgjigjet (1)

Kevin
Kevin
  • Moderator
more options

You would be best to ask the Firefox for Android developers at https://chat.mibbit.com/?server=irc.mozilla.org&channel=%23mobile they can be best reached from 8 AM pacific to 6 PM pacific during the work week.

As I understand your question you would need https://bugzilla.mozilla.org/show_bug.cgi?id=799631 to be fixed.