Any sort of roadmap for Xenforo 2.3 ?

My mistake.

It will be in 2.3 but based on the existing style.

It's 3.0 which comes with a completely new style.

I'm assuming this is just an additional style that can be selected, and the answer is no, but does it use prefers-color-scheme so it'll inherit from your device's preferences? (Question applies to both 2.3, as well as 3.0. Assuming the answer is no for 2.3 since I'm not sure how that would be feasible, but really hoping it's the case for 3.0)
 
Along with a bunch of major performance improvements and new features that are on the slate for 2.3, one of the main things on our list to do was a totally new master style. This has been largely my domain, and I have to say I'm really looking forward to unveiling it.
Will this help address the upcoming "Interaction to Next Paint (INP)" metric that google is planning to introducing for search scoring?
 
Will this help address the upcoming "Interaction to Next Paint (INP)" metric that google is planning to introducing for search scoring?
I hope it will address all Core Web Vital metrics and improving page speed.
 
I'm assuming this is just an additional style that can be selected, and the answer is no, but does it use prefers-color-scheme so it'll inherit from your device's preferences? (Question applies to both 2.3, as well as 3.0. Assuming the answer is no for 2.3 since I'm not sure how that would be feasible, but really hoping it's the case for 3.0)
We now have the ability to set style properties as supporting variants, so you can have an alternate version of particular style properties that will be activated in the presence of prefers-color-scheme. This is for 3.0 and 2.3.
 
Yes, this I understand. Let me put some more nuance in my statement:
There seems little point in investing in the creation of essential XF2 addons IF these introduce UI/styling elements, when XF3 is on the way. Because the UI and styling would have to be redone.
What do the developers think about this dilemma?

There's no real difference between this argument about styles for 2.3 vs 3.0 or any other major upgrade which introduces breaking changes (eg 1.5 vs 2.0) - addon developers will need to decide where to put their efforts - creating for the existing version, or targeting the new version.

This is always going to happen for every major release with breaking changes.

In the case of 2.3 vs 3.0, given the codebase isn't changing significantly, the amount of work to migrate addons to 3.0 should be significantly less (relatively speaking) than they were for the equivalent 1.5 to 2.0 upgrade where both the codebase and the styles basically needed to be re-written from scratch.
 
I don’t get the “new editor” hype. What is it with the new editor? I tried searching for it over here but can’t find anything about it!

Mind telling me about the benefits of the new editor? 👀

it's incredibly broken, especially on Firefox. Plus it doesn't have the functionality to upload multiple images at a time by dragging them, which IMO was a huge loss

And what would the new editor be?

Literally any other, including the old one lol. Tiptap has been nice for a couple projects I've tried it on, but anything usable would be good.
 
You can always upgrade firefox!
Upgrading Firefox won't help. Downgrading to another browser might fix a few issues though.

To put some perspective on this and other issues, today I linked a couple of important posts made here on a forum I admin using Firefox. Due to unfurling issues (not a bug... really? Well read on...) Kier's important announcement displayed as 'Hop on the ignore train will you?'.

Attempts to copy and paste the content into my post resulted in the loss of all formatting and it went down hill from there.

So to the cut to the chase, it's disappointing not to hear any mention of the current editor's future because I was hoping the release delay was because it didn't have one.
 
Last edited:
Upgrading Firefox won't help. Downgrading to another editor might fix a few issues though.

To put some perspective on this and other issues, today I linked a couple of important posts made here on a forum I admin using Firefox. Due to unfurling issues (not a bug... really? Well read on...) Kier's important announcement displayed as 'Hop on the ignore train will you?'.

Attempts to copy and paste the content into my post resulted in the loss of all formatting and it went down hill from there.

So to the cut to the chase, it's disappointing not to hear any mention of the current editor's future because I was hoping the release delay was because it didn't have one.
Sounds like a caching issue maybe because on the other computers at uni it seemed to be a really bad caching issue.
I use firefox as it's great with my iMac desktop computer. I have auto upgrade on my computer.
I don't have any issues with the Editor on my computer but i do on other people's computers such as my local uni's computers.
 
@Chris D re this discussion about the editor, wouldn't it perhaps be a good idea to write your own custom one that does everything you want and works in the same awesome way that the rest of XF does? This way you don't have to put up with the bugs, quirks and limitations of a third party one.

Given the development work required, perhaps it could be released with 3.0, 3.1 etc.

Waddya think?
 
@Chris D re this discussion about the editor, wouldn't it perhaps be a good idea to write your own custom one that does everything you want and works in the same awesome way that the rest of XF does? This way you don't have to put up with the bugs, quirks and limitations of a third party one.

Given the development work required, perhaps it could be released with 3.0, 3.1 etc.

Waddya think?

The current editor is a massive problem, but I think that it highlights the problems that the XF team would have if they were to take this in-house. The more features you add to the editor the more problematic it becomes making it work reliably with different browsers, different releases of browsers and different operating systems. I can see why they would want to use a 3rd party product for this so they can concentrate on the core.

Froala has caused problems for many of our users and been unpopular with them since XF started using it though and needs replaced even if it is with something simpler and less fully featured.
 
Will this help address the upcoming "Interaction to Next Paint (INP)" metric that google is planning to introducing for search scoring?
Some of the earliest work on 2.3 was towards improving Lighthouse metrics, though we may need to revisit this again with INP in mind.

Bearing in mind this is only "lab data" from relatively barebones local installations, here is a mobile performance score comparison of the thread view between 2.2 and 2.3 on identical server configurations:

screenshot-4e4dDs.png screenshot-Ri1kK4.png
 
Some of the earliest work on 2.3 was towards improving Lighthouse metrics, though we may need to revisit this again with INP in mind.

Bearing in mind this is only "lab data" from relatively barebones local installations, here is a mobile performance score comparison of the thread view between 2.2 and 2.3 on identical server configurations:

That’s a good improvement.
 
Back
Top Bottom