zork

Still not fixed...

Bug not fixed.

You don't understand what you're writing about. The bug is present in the default theme. In any, both light and dark.

Hi, Sandra! In OS (LTSC 1809) theme is system. Nothing changed. Resolution 1920x1080. The bug appeared since the first beta 6.2

interface customize icon is not shown correctly (padding error)

Internal Google translator is gone forever? RIP? Jeff, WTF is going on? You are destroying Chrome functionality. What for?

You are welcome!

You do not understand what this is about..

You are welcome!

Respect other members - use Google Translate

Speak English.

Jeff, One and very important question - M6 interface can be changed as M5? The main scripting engine will be Sciter (Htmlayout) as before?

5.2.5.600-beta update.

Translator module has changed in 5.2.5. The updated skin in beta stage. I will upload it ASAP.

Tab Manager is extension and takes translation from corresponding strings in extension locale folder. You can make it by yourself. It will be faster. For example, for the Russian language: [lang] app.title=Менеджер вкладок app.description=Удобное средство просмотра и управления вкладками paneltitle=Менеджер вкладок app.tabManager=Менеджер вкладок app.closeAllTabs=Закрыть все app.refreshTabList=Обновить все Or you can replace original addon with new one from the attach. ru-ru.ini tabmanager.mxaddon

5.2.3.3000 update. Tabbar fix for Win10.

5.2.3.1000 update. Skin minor changes. New sound, lock and sidebar icons. Some bugs fixed.

5.2.0.2000 update. Skin minor changes.

5.1.6.3000 update. Slim tabs added. Skin minor changes.

5.1.6.1000 update. Skin minor changes. Interactive аvatar button added to navbar (can be hidden in menu).

You're wrong. You're right. 5.1.5.2000 update with some mods (icons in tab menu added)

New Arowana skin for Maxthon 5.2.5.600-beta. Skin is similar to my Snapper 2. Slim navigation and statusbar. Search engine in address bar, new menu, modded tab menu and a lot of other features. Enjoy. Arowana_5.1.4.3000_forum.7z Arowana_5.1.5.2000_forum.7z Arowana_5.1.6.1000_forum.7z Arowana_5.1.6.3000_forum.7z Arowana_5.2.0.2000_forum.7z Arowana_5.2.3.1000_forum.7z Arowana_5.2.3.3000_forum.7z Arowana_5.2.5.600b_forum.7z

The internal command cmd.lockBrowser is not new. It was in M4. And you are right - it wasn't listed in SDK, but it works. Other commands starting with cmd.xxxx not working in extension too. I would very much like to hear comments from dev's on this issue.

Does anyone know how to execute a browser lock command from an extension? The command works fine from the menu item, it can be assigned to a button, but it does not start from the extension. What could be the reason? For example, to run from the icon, the code will be like this: <div class="item lock" mx-click="cmd.lockBrowser" title="$cmd.lockBrowser$" > <div class="icon"/> </div> But in the extension the same code doesn't work: "actions": [ { "type": "mxcmd", "entryPoints": ["toolbar"], "cmd": "cmd.lockBrowser" } ] And without the cmd too: "actions": [ { "type": "mxcmd", "entryPoints": ["toolbar"], "cmd": "lockBrowser" } ] What's wrong???

Wilser, you forgot one thing - ABP has a separate icon with different stages. To exclude it you need to use this code: .quicktools .item:not([mx-object="adblock-toolbar"]) .icon{ foreground-image-transformation: colorize(white); }