Addressing Intl.Segmenter Compatibility Issues in Construct 3 Projects

0 favourites
  • 5 posts
From the Asset Store
Casino? money? who knows? but the target is the same!
  • Hello Construct 3 Community,

    I'm encountering a compatibility issue with my Construct 3 project related to the Intl.Segmenter API. When users access the game using certain browsers, particularly older versions of Firefox, they receive the following error message:

    Software update needed This content is not supported because your device's software appears to be out-of-date. Try installing any available software updates. Alternatively, try on a different device. Missing features: Internationalization support (Intl.Segmenter) User agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

    Context:

    • I have not manually implemented Intl.Segmenter in my project.
    • There are no custom scripts added.
    • The project primarily uses Construct 3's built-in features.
    • The problem appears with the new version of Construct3. It didn't happen in previous versions. It only happens with the latest update.
  • I know saying this isn't exactly helpful but this error quite directly tells the user what the problem is and how they can fix it. Is that... not good enough?

    I'd assume the Internationalization support is used by constructs build-in Internationalization plugin. Did you use that plugin? Either way Construct probably checks for support and if it isn't supported, shows this error. It's kinda weird though that only a recent update has caused this error to show up, considering the internationalization plugin has been implemented for a good while now.

  • I have the same issue as my colleague: same context, same project. A few weeks ago, it was working, but with the latest update of Construct 3, it no longer works on Firefox versions prior to v125, Chrome versions prior to 87, and Opera versions prior to 79. Previously, it worked on these systems. Any solution?

  • Construct does now require Intl.Segmenter support in the browser. Firefox only added support for this in v125, but that was released in April last year - the current version is v134. The latest Extended Support Release (ESR) is v128 released back in October, so even those sticking to ESR releases have a supported option. Therefore we deemed support good enough to rely on it in Firefox. The error message advises what to do - the browser is out of date and needs updating.

    Support in Chrome was indeed added in v87, but that was released over four years ago, so I don't really know why anyone would still be running such an old version of Chrome unless their entire system is no longer supported. In general it's just not feasible for us to support old browsers forever - the web platform keeps improving and we want to make the most of that, and sometimes that means increasing the minimum requirements. With Chrome and Safari we try to make sure we're compatible with around 4 years of past releases. In this case we made an exception for Firefox and brought the minimum version up as it was the last browser to support a key feature that allowed us to make internationalization improvements, we waited long enough for the latest ESR release to support it, and these days Firefox usage is (sadly) much lower than Chrome or Safari so the impact of such a change is reduced.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • It would be highly beneficial to at least have the option to choose the language of the warning or configure it. Construct 3 is used worldwide, not just in English-speaking countries, and many users may not understand the current message.

    One possible reason someone might still be using outdated browser versions is that they are installed on government-provided devices, such as interactive whiteboards in public institutions used by thousands of teachers. These devices are typically not managed by the end user, making updates and modernization significantly more challenging.

    If that is the case, and upgrading them is not a feasible option, I understand that there may be no solution for these specific devices under the current Construct 3 requirements.

    Thank you nonetheless for the clarification and for the great work you do.

    Best regards.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)