[locale(s)]
- Greek (el) translation updated (thanks to George M.)
- Upper Sorbian (hsb) translation updated (thanks to milupo)
- Lower Sorbian (dsb) translation updated (thanks to milupo)
- Czech (cs) translation updated (thanks to poljos)
- Slovenian (sl-SI) translation updated (thanks to Klofutar)
- Polish (pl-PL) translation updated (thanks to Mrere)
- Estonian (et) translation updated (thanks to Maidur)
- Chinese (zh-CN) translation updated (thanks to Cye3s)
- Spanish (es) translation updated (thanks to strel)
- Russian (ru) translation updated (thanks to Alexei)
- Ukrainian (uk) translation updated (thanks to Sacredwheels)
[fix(es)]
- squared pinned tabs: glitch with tab toolbars overflow state
- Win10 & squared tabs v2: glitch in maximized mode
- Win10 & Fx47: option to display OS titlebar background
- MacOS & big icon mode: back and forward buttons
- pinned tabs & 'titlechanged' status
- pinned tabs: image padding in some cases
[add-on compatibility]
- 'FireIE' add-on: padding in some cases
- 'Cache status' add-on: status position (not on prefwindow)
-> about:config > extensions.classicthemerestorer.cstatextlb >
-> true: location bar (CS add-ons default position)
-> false: CTRs status area (old default position)
[new option(s)]
- (Fx45+) General UI 1: HTML5 full screen warning
-> switches full-screen-api.warning.timeout between 3000 and 0
-> switches full-screen-api.warning.delay between 500 and 0
- (Fx48+) Location bar (1): alternative 'autocomplete popup' (experimental)
-> Preview:
http://i.imgur.com/w2LXlAu.png[general change(s)]
- tweaks for 'hide i-icon' option
- unlocked tab height settings: up to 250 px possible
-> this will cause glitches with some tab variations
- old search: popup width based on search input width
-> (old behavior) extensions.classicthemerestorer.osearch_iwidth > false
- add-on manager options: font size tweaks for add-on description
Note - 'Add-on Compatibility Reporter' add-on
Do not use the mentioned add-on to report potential issues, because...
1) ...most reports do not contain any information or issue description.
2) ...there is no way to respond or to verify such reports.
3) ...reports do not provide enough system and configuration information.
Use CTRs support forum or Github to report potential issues.
Japanese locale
According to AMOs statistics there are over 40K Japanese CTR users. Is anyone volunteering to update ja locale? Outdated locales files are on Github and on current CTR beta builds. If anyone wants to work on ja locale, please use Github or contact me via email. At the current state it was not fully suitable for CTRs release build.
https://github.com/Aris-t2/ClassicThemeRestorer/blob/master/xpi/locale/ja/options.dtd