Awaiting an answer SP Page Builder

SP Page Builder Backwards Compatibility

Asked by Alvaro 1 year ago Last activity 1 year ago

Hello.
How many years of backwards compatibility do you have in SP Page Builder?

Because I'm testing websites with SPPB 5.5.2 and none of the javascript-based functions like modal, gallery, slider work in 2017 browsers like Firefox 55 or Chrome 57. But if I test sites that haven't been updated and are still using SPPB 5.4.x, they all work normally.

It's understood that modern technology must be used for the editor, but for the front-end it must be backwards compatible.

I hope for answers and opinions, greetings

4 replies

Toufiq Senior Staff

1 year ago

Hi there,

We strive to maintain backward compatibility in SP Page Builder as much as possible(Joomla Initial version to 5 is running). However, it's important to note that JavaScript is a browser-side scripting language, and older browsers may not support modern JavaScript features used in the latest versions of SP Page Builder.

We recommend using the latest browser versions for optimal performance. However, if you're experiencing issues specifically with front-end editing, please provide Joomla administrator access via hidden content, and we'll be happy to investigate further.

Best regards,

Toufiqur Rahman (Team Lead, Support)

Paul Frankowski Senior Staff

1 year ago · edited

BTW

Let's not forget the simple fact that Chrome as well as Firefox update themselves for important reasons. If someone has an antique Windows XP, where browser updates are no longer possible, I'm sorry but they are harming themselves by putting themselves at security risk by still using Internet.

Backward compatibility comes at a price and is not always beneficial to all users.

This is my private opinion.

Alvaro Asked this

1 year ago

Hi Toufiq and Paul.
I understand what you're describing and your opinions, but you know this is handled by industry-standard or average compatibility values.

The requested project required 10 years of compatibility, but we agreed to 9 (because SPPB 5.4.x was compatible). They said OK, we haven't had any problems with CSS. The problem is with Javascript, which in the 2017 browser console (version 55) gives errors such as "Uncaught SyntaxError: Unexpected token." And this isn't in the editor, but in the public area where any visitor has access.

That's why I'm asking, how many years of compatibility are you working with?

The question isn't about me; my computers are modern with the latest versions. The question is about our clients and visitors. Bringing Windows XP here makes no sense. No one mentioned 2014 or earlier.
Regards

Toufiq Senior Staff

1 year ago

We do not provide backward compatibility for outdated or unsupported browser versions. However, we do ensure backward compatibility for Joomla, maintaining compatibility with previous versions to offer a seamless experience for users upgrading their Joomla sites.

Alvaro Asked this

1 year ago

Hi Toufiq.
You said "We do not provide backward compatibility for outdated or unsupported browser versions." Okay, so since what browser version has SPPB been supported? Since what year? That's my question from the start. Please ask the development team.

I think it's clear we're talking about JavaScript here.

Paul Frankowski Senior Staff

1 year ago · edited

9-10 years, wow.... this is not software for OS, but extensions for CMS and browsers.

Current version of:

Firefox for Windows is 136.x
Chrome for Windows is 134.x

Simple question, would you pay extra for old browser legacy? probably no.

Besides, Windows 10 premiered on July 2015. Which means that everyone who has this system gets Chrome and Firefox updates automatically. Also, I don't understand how someone can still have browser versions from a few years ago having access to Internet.

The only explanation is that someone is sitting in some office and there is the IT Specialist who decides what he/she is allowed to install.

Alvaro Asked this

1 year ago

Hi Paul.
From the start, I asked a question, and you haven't answered it. You've preferred to talk about details that aren't important. If you don't know, you can ask the development team. I don't think they develop without considering backwards compatibility, even for a year. They should know.

When I tell you why they aren't compatible or ask you to be compatible, your answers would make sense. But I only asked one question: How many years of backwards compatibility does SPPB have?

And we're only talking about Javascript.