Aris
Aris
@ExE-Boss Great job!
@Fuzzy-Logik @MelchiorGaspar May I suggest to test Firefox 52 ESR? It will receive security updates until summer 2018, what will be far better than staying on Firefox 56. In fact...
Thanks for the note. I will remove this entry and also "Getting started" and "Health Report". All three are useless in Basilisk and Waterfox.
I was under the impression a notification might be enough (at least in threads one participated in the past). Discussions make at least direct replies easier. 
It depends on how many changes are required. I have not tested WF68 yet, but if only the install manifest hast to be rewritten, I will do it If more...
Its not only about the CSS required for v68, its about the add-on functionality itself. I do not have the time or the will to rewrite CTR, sorry. Feel free...
Not sure how to force the box to appear right now for testing. Try this code in `userChrome.css`, it might be the "box": ```css #tab-notification-deck-template { -moz-box-ordinal-group: 100 !important; }...
Install CTR_v1.7.7.7.2test.xpi test build from here: https://github.com/Aris-t2/ClassicThemeRestorer/releases/tag/1.7.7.7
OK then, next update will contain this fix. Note, CTR updates for Waterfox are only provided here on Github.
No, CTR was never build into Waterfox. There was a CTR fork called CyberCTR, which was part of Cyberfox. The Legacy Extensions Database only contains files, that were distributed previously...