Will CTR be ported to work with Waterfox 68?

[Telmesomething]

I've been reading about changes being made to Waterfox 68 and was wondering if CTR will be ported to work with the new version?

[Peacock365]

The first Alpha of Waterfox 68 has been officially released:

• https://github.com/MrAlex94/Waterfox/releases/tag/68.0a1

Relevant documentation:

• https://github.com/MrAlex94/Waterfox/wiki
• https://github.com/MrAlex94/Waterfox/wiki/Engage-the-new-overlay-loader
• https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57
• https://github.com/MrAlex94/Waterfox/wiki/List-of-changes-in-Gecko-up-to-version-68

I also hope that CTR gets ported to it. I rely on it.

[Aris-t2]

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 has to be done, I'm not going to rewrite the add-on.

[Peacock365]

@Aris-t2

I assume you'd also have to apply CSS code that is compatible with Firefox 68, basically the same code you've already created for CustomCSS for Firefox.

[Aris-t2]

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 to fork it.

[Peacock365]

@Aris-t2

One thing that I hate about all Firefox versions since Firefox 57 is that you have to create a userChrome.css file, injecting the CSS manually, if you want to change anything about the UI. It used to be easy - open the CTR preferences, set some checkmarks, done. It was very user-friendly and efficient. Now it's an absolute mess, and not at all a good experience. I don't blame you for this, as it's clearly Mozilla's fault. But playing the blame game doesn't really change anything about the bad user experience.

Hopefully CTR will reappear on Waterfox 68, dealing with userChrome.css is somewhat tiring, to the point where I switched to Firefox ESR, so that I don't have recreate parts of the CSS all over again whenever a new Firefox release happens to break it.

CTR: Good user experience, not tiresome.
userChrome.css: Bad user experience, tiresome.

That's the way I see it. Again, I don't play the blame game here, as it's clearly Mozilla's fault. I am just saying that an actual CTR for Waterfox 68 would make everything easier, to the point where I'd like to use your CSS modifications (of which some are extremely useful to me) again. User friendliness is something I value, especially after the experience that something which was easy to do once has become a mess recently.

[L0que]

So you're saying there is a chance? We will all cross our fingers then that it's only the install manifest that needs updating. CTR is simply priority #1 extension for many of us and a deal breaker as far as the decision to update a browser.

[Squall-Leonhart]

the best path would be to integrate CTR as native capability of WF68

[human-being-1]

this might be a bump but i heard that it will support XUL

[Telmesomething]

@NanhuGITHUB,

Not according to ghacks it won't (unfortunately).

[human-being-1]

its a alpha release, they might fix it with code from ff56.
if they dont we can always use basilk

[Telmesomething]

Basilisk doesn't support any addons which can be used to turn pale grey fonts on sites black. I use Legibility which although it's WebEx still works on the current version of Waterfox but not on Basilisk. I posted on the Pale Moon forum about that but they told me that Basilisk won't support any WebEx.