Aris
Aris
I doubt future browser changes will improve the situation here. Switching to `top_toolbar_colors.css` and dropping `top_toolbar_OS_accent_colors.css` might be the better solution for now. My post above missed some screenshots. Now...

Add-ons as they are now work fine in Basilisk. Some of my add-ons I already posted on PaleMoon repository too.
I'm not sure this can be fixed in CTR. Using e10s Firefox fails to forward urls via window.open(), if the location bar is on a non-visible toolbar instead of being...
For such sites to work you can either disable e10s or move the location bar back to navigation toolbar. I'm not sure how or if Mozilla will handle this, but...
Unfortunately not. Too many internal listeners look and search for the "default" location bar and its contents (identity box, buttons, input box). CTR already offers a second location ar, but...
CTR is not under active development anymore.
Palemoon does not need CTR. All important CTR features are part of Palemoon by default, because Palemoon never switched to Fx29+ UI.
"Some kind of theming" will be possible even after Firefox 57 arrives, but it will be highly restricted. No "I can do what I want" anymore with CSS, JavaScript or...
Only in theory. The massive changes will break them anyway. See https://blog.mozilla.org/addons/2017/04/05/compatibility-firefox-54/#comment-223852