XF 2.4 general discussion, feedback, complaints, random off topic posts, etc.

[Alpha1]

No, it would represent a recurrence and pattern of missed and back-pedalled version commitment. 3.0 was previously stated as being released by Jan '25.

It seems to me that the style is not nearly ready for release or else the release would not have been pushed back. I'd rather see something well thought out at a future date, than something underwhelming tomorrow that will only result in disappointment and backlash.
There are many popular suggestions in the suggestion forums that are related to styling, templates and page output:

• Don't hide pagination at the top of threads on mobile
• Leaner sized css.php for better pagespeed
• Use semantic paragraph <p> tags in post content instead of line breaks <br> (Accessibility, Semantics, Bug Fixing, Styling, SEO?)
• Language Nodes
• Forum Icons
• Apply Name Change to quotes & user mentions (GDPR)
• Revitalize layout for competitive landscape to increase traffic and retention
• Page Builder: drag n Drop widgets

Hopefully some of these will be addressed in XF3.0
Getting leaner HTML output with less DOM size to further boost performance and more structured data would also be nice to see.
I think people will have high expectations for a new style. It should bring XenForo into current design expectations.

Thread 'Reduce HTML output to boost performance & SEO'

Sep 17, 2024

XF2.3 has greatly boosted performance. I hope that further improvements can be made by optimizing the HTML output. A GTMetrix report for XF2.3 shows excessive DOM size with almost 3400 elements on a page and 103 child elements :

https://gtmetrix.com/reports/xenforo.com/A5Ttit73/

Maybe waiting time for the page to load can also be reduced?

I hope that addon developers will posts their feedback on further boosting performance to this thread.

• Alpha1
• better seo google ranking page html page optimization pagespeed performance seo
• Replies: 9
• Forum: XenForo suggestions

• 

 

[Mouth]

It seems to me that the style is not nearly ready for release or else the release would not have been pushed back. I'd rather see something well thought out at a future date, than something underwhelming tomorrow that will only result in disappointment and backlash.

Don't disagree. But, the 3.0 release and new style was touted approx. 12 mths ago. Then approx 2 mths ago it was going to be the next release after 2.3 and due by January. Now it's been pushed back, and 2.4 inserted, with 2.5 also touted. It's reasonable to ask why the delay and push-back, without getting smart ass developer response.

 

[mjda]

Don't disagree. But, the 3.0 release and new style was touted approx. 12 mths ago. Then approx 2 mths ago it was going to be the next release after 2.3 and due by January. Now it's been pushed back, and 2.4 inserted, with 2.5 also touted. It's reasonable to ask why the delay and push-back, without getting smart ass developer response.

@Chris D has already mentioned in another thread that 3.0 got slowed down by some back end changes.

No, it was an aim. We’ll be giving an update this coming week.


This is mostly all semantics but the core design hasn’t been changed. We got slowed down by some backend changes we needed to make. But on the whole work has been ongoing in the implementation.

 

[Starbucks]

We're back at the "Why is it taking so long" phase.
This time I won't join the ride, but I will be watching.

 

[Paul B]

 

[Sim]

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[Starbucks]

It’s part of the cycle, soon you’re up to clean-up the thread. It’s all in the playbook!!

 

[robdog]

Don't disagree. But, the 3.0 release and new style was touted approx. 12 mths ago. Then approx 2 mths ago it was going to be the next release after 2.3 and due by January. Now it's been pushed back, and 2.4 inserted, with 2.5 also touted. It's reasonable to ask why the delay and push-back, without getting smart ass developer response.

If we look at it from a simple backwards compatibility perspective, we can deduce the incremental releases were to soften the blow of v3.0 introducing breaking changes. So as we get more releases, v2.3, v2.4, v2.5, etc... it will continue to make the transition into v3.0 easier. My other assumption is that we are getting some updates that may have been held back for v3.0 in these incremental releases.

Of course the dev team can let me know I am full of it, but that is me putting on my developer hat.

 

[Paul B]

That's largely correct.

 

[MesterPerfect]

Tiptap doesn’t have any styling by default. Literally none. It doesn’t provide any UI, in fact. No toolbar, no buttons.

The entire UI you will see is built by us.

This makes me concerned about the accessibility support in the UI you'll be designing .

 

[Chris D]

Us building the UI ourselves is by far the best outcome for accessibility.

I’m not promising we’ll get it perfect first time but as it is our own UI we can iterate on it and do what needs to be done to ensure it is accessible for everyone.

 

[Mr Lucky]

Us building the UI ourselves is by far the best outcome for accessibility.

I couldn't agree more, and we have direct and easy feedback to the actual developers via bug reports and suggestions - has anyone tried that with Froala?

 

[Chris D]

has anyone tried that with Froala?

Only a few hundred times

 

[Aivaras]

Us building the UI ourselves is by far the best outcome for accessibility.

I’m not promising we’ll get it perfect first time but as it is our own UI we can iterate on it and do what needs to be done to ensure it is accessible for everyone.

This is indeed a big advantage. It was the primary driving force behind our decision to develop our own custom style (that significantly differs from the default one), using only the tools available in the ACP. It worked out very well, and I’m confident we’ll be able to replicate the same experience with v3.0.

 

[MesterPerfect]

Us building the UI ourselves is by far the best outcome for accessibility.

I’m not promising we’ll get it perfect first time but as it is our own UI we can iterate on it and do what needs to be done to ensure it is accessible for everyone.

"I'm glad to hear your positive response regarding accessibility! If I want to open a discussion to address screen reader accessibility issues that users are experiencing with XenForo, where would be the best place to do that?"

 

[MesterPerfect]

This is indeed a big advantage. It was the primary driving force behind our decision to develop our own custom style (that significantly differs from the default one), using only the tools available in the ACP. It worked out very well, and I’m confident we’ll be able to replicate the same experience with v3.0.

Does your custom style have more accessibility support?

 

[Aivaras]

Does your custom style have more accessibility support?

No, it does not. I was emphasizing the importance of this bit:

Us building the UI ourselves […]

 

[MoopyForums]

Will the new editor be able to accept GIFs from Google keyboard as an input, like WhatsApp and Discord are able to?

 

[Chris D]

Is the current editor not able to?

 

[MoopyForums]

No, you get a warning saying "this app does not support GIFs here"