<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Remove access to Firefox Persona in favor of self-hosted extensions" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123831#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Remove access to Firefox Persona in favor of self-hosted extensions" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123831">bug 123831</a> from <a class="email" href="mailto:muhammetk@gmail.com" title="Muhammet Kara <muhammetk@gmail.com>"> Muhammet Kara</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=123831#c0">comment #0</a>) > Since Mozilla changed the API again access to themes is broken (6.2). We > should move forward, remove the dialog to download themes from Mozilla and > provide our own extensions for it. I was already up for disabling that dialog, and maybe for removal later. But since the Moz Themes are no longer compatible with our implementation (not only an API change any more, but matter of missing files), I second this approach. Better to get an ACK from ESC first. (In reply to Peter Maunder from <a href="show_bug.cgi?id=123831#c1">comment #1</a>) > I would welcome a facility to enable me to select my own theme that I have > created and sits on my system that contains my LibreOffice configuration. I > use to able to do this using the Olen Expert Configuration. I am sure this > would make a popular Extension or Personalisation option. That's the intention with the extension approach. Anyone can create an extension with a ready-to-use extension template.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>