Version 1.3.3beta8

[locale] Polish (pl-PL) translation updated (thanks to Mrere)
[locale] Ukrainian (uk) translation updated (thanks to Sacredwheels)
[locale] French (fr) translation updated (thanks to David V.)

[new] gray icons for appbutton on toolbar option

[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
either, 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.

1.3.3 beta 7

[fix] rounded tabs + custom colors + TabMixPlus: active tab appearance
TMP currently breaks active tab ui on Fx39+. This fix should override
that glitch when using custom color options provided by CTR.

1.3.3 beta 6

[fix] Fx29-39: CTR button appearance + high dpi values

[change] lw-themes + tabs not on top v1 + Fx38+: line below tabs toolbar

[change] removed option "remove underline on e10s tabs"

[change] internal changes to minimize amount of new validator warnings
--> doesn't seem to break anything, but still needs more testing

1 files changed, 0 insertions, 44 deletions

diff --git a/xpi/content/aboutnewtab.js b/xpi/content/aboutnewtab.js
deleted file mode 100644
index 69c271a..0000000
--- a/xpi/content/aboutnewtab.js
+++ /dev/null
@@ -1,44 +0,0 @@
-"use strict";
-/*
-	Clicking 'newtab customize button' simulates toggling newtab page visibility like in Fx28.
-	- If newtab page is active, deactivate it.
-	- If newtab page is deactivated, activate it.
-	- Always make sure 'enhanced' newtab page stays disabled.
-	- Remove buttons 'active' attribute: not needed in this mode.
-	All this only happens, if the corresponding 'alternative new tab page' option
-	is enabled on CTRs options window. It is disabled by default and does not interfere
-	with newtab page.  
-*/
-Cu.import("resource://gre/modules/Services.jsm");
-    
-function ctraddon_toggle_newtab_page(){
-  if(Services.prefs.getBranch('extensions.classicthemerestorer.').getBoolPref('alt_newtabp')) {
-    try{
-	  Services.prefs.getBranch('browser.newtabpage.').setBoolPref('enhanced',false);
- 
-	  if(!Services.prefs.getBranch('browser.newtabpage.').getBoolPref('enabled')==false)
-		Services.prefs.getBranch('browser.newtabpage.').setBoolPref('enabled',false);
-	  else
-		Services.prefs.getBranch('browser.newtabpage.').setBoolPref('enabled',true);
-	} catch(e){}
-  }
-  
-  setTimeout(function(){
-	try{
-	  if(document.getElementById("newtab-customize-button").hasAttribute('active'))
-		document.getElementById("newtab-customize-button").removeAttribute('active');
-	}catch(e){}
-	try{
-	  if(parseInt(Services.prefs.getBranch("extensions.").getCharPref("lastAppVersion")) >= 40)
-		document.getElementById("newtab-window").setAttribute('fx40plus',true);
-	} catch(e){}
-  },200);
-
-}
-	
-if(Services.prefs.getBranch('extensions.classicthemerestorer.').getBoolPref('alt_newtabp')) {
-  try{
-	if(parseInt(Services.prefs.getBranch("extensions.").getCharPref("lastAppVersion")) >= 40)
-	  document.getElementById("newtab-window").setAttribute('fx40plus',true);
-  } catch(e){}
-}
\ No newline at end of file