This repository has been archived by the owner on Feb 17, 2021. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[locale] Polish (pl-PL) translation updated (thanks to Mrere) [locale] Chinese (zh-CN) translation updated (thanks to Cye3s) [locale] Ukrainian (uk) translation updated (thanks to Sacredwheels) [locale] French (fr) translation updated (thanks to David V.) [locale] Greek (el) translation updated (thanks to George M.) [fix] minor glitch with 'alt. new tab' page and 4+ rows [fix] minor tweaks for 'small button' mode [fix] disable 'context menu entries' to remove buttons, when button in urlbar [fix] big icon option: bookmarks and panel menu buttons on nav-bar [fix] rounded tabs + custom colors + TabMixPlus: active tab appearance [fix] Fx29-39: CTR button appearance + high dpi values [fix] Fx40+: Windows + small buttons mode + higher dpi res than 100% [fix] Fx40+: glitches with 'curved tabs alt' option [fix] Fx31.x: 'hide toolbar context menu entries' option [fix] Faviconize tab add-on + tab close (forced) [fix] MacOSX + HiDPI + star/feed button in location bar [new] gray icons for appbutton on toolbar option [change] lw-themes + tabs not on top v1 + Fx38+: line below tabs toolbar [change] removed option "remove underline on e10s tabs" [change] Windows + tabs not on top v1 + lw-themes + Fx38+ --> (re)added missing line below tabs toolbar [change] additional note for 'Pocket' checkbox on preference window [change] minor pref window tweaks for RTL locales [change] reduced size of exported .json file (thanks to Toady) [change] removed a few duplicated menu items from appmenu [change] improved support for 'Faviconize tab' add-on [change] Fx40+: tweaks for 'prevent dev theme' option [change] Fx40+: (re)added option to prevent developer theme from being enabled [change] Fx40+: removed temp. dev theme changes [change] Fx40+: tiny tweaks for developer theme & appbutton on titlebar Validator / add-on signing [change] internal changes to get rid of new validator warnings [change] meeting add-on validators new rules --> removed/changed/altered some features, see text below Attention – important changes :-( Most of you have heard of Mozillas new add-on signing process. As a part of this process, new rules (what add-ons are allowed to do and what not) were added to Firefox and Mozillas add-ons validator. Some of these new rules forbid add-ons to change default Firefox preferences within a script/function like OS/Fx titlebar, ‘new tab’ page and tab clip width or (some) developer theme preferences, even if this is only done optionally after a user selects a corresponding CTR option. The result of this act is either play by new rules or not play at all, meaning either CTR drops supporting those features or no new CTR versions can be uploaded anymore. (I’m currently not even able to upload the already validated(!) and signed(!) version of CTR to the validator anymore). I had to remove some CTR features to even being able to upload a new beta (!) version of CTR. See screenshot: http://i.imgur.com/1Q3paEh.png Explanation what changed (some preferences can still be altered manually through CTRs prefwindow): - ‘New tab’ page: alternative ‘new tab’ page option will still modify the ‘new tab’ pages appearance, but switching between its ‘on’ and ‘off’ states will not be possible with one click anymore. Switching required modifying a default ‘new tab’ preference to true/false, but add-ons are not allowed to even offer switches for the default about:config preferences ‘browser.newtabpage.enabled’ and ‘browser.newtabpage.enhanced’ anymore. Having just a text (!) string as a label is already forbidden. - ‘Tab clip width’ only affects ‘tab close on all tabs (forced)’ option. Its value will not get changed automatically to ‘1’ btw. ‘140’ anymore, but a new textbox allows changing this value manually now. - Switching to ‘appbutton on titlebar’ will not enable Fx titlebar automatically anymore, if OS titlebar is active, but there has been always a switch for a change on CTRs prefwindow. - Developer theme preferences on Fx35-40 have to be switched manually. Although Fx 40 (Aurora/DevEdition) handles dev edition theme inside add-ons manager, it still wrongly keeps the older developer theme preferences, which have to be disabled manually in some cases to not interfere with CTRs settings. Additionally the preference to prevent developer theme from being enabled had to be removed too (Fx35-40). Fx41+ is (currently) not affected by this. If you do not like these changes, keep in mind I do not like them too, but they are necessary to keep this add-on alive. If you really need someone to blame for this, please use Mozillas default contact channels and report your thoughts about add-on signing and recent rule additions to them.
- Loading branch information
