deblan/side_menu

Fork 9

[Bug] Side menu not appearing in Firefox 115 #464

New issue

Closed

opened 2025-12-23 19:21:11 +01:00 by tty-13 · 5 comments

tty-13 commented

2025-12-23 19:21:11 +01:00

Environment

Custom menu version: 5.1.3 (irrelevant)
Nextcloud version: 32.0.3 (irrelevant)
Web browser and version : Firefox 115 and maybe some older versions of Chromium based browsers, etc.

Configuration

{
  irrelevant.
}

Steps to reproduce

Hey there :)
Found another bug, fortunately this time I could work my way around it.
I manage a small nextcloud instance with users that have rather outdated or not-so-outdated hardware. Two of them are on MacOSX 10.14 since Apple does not want them to upgrade their computers, rather forcing them to buy new hardware.
Thing is, the custom menu is not visible on their hardware.
I could reproduce this bug in a Debian VM by installing the last Firefox 115 available : same problem, the custom menu does not appear.

This is due to Intl.Segmenter being too recent for Firefox 115.
According to this, it is supported only since FF 125.
In older versions, it throws this error in the console :
Uncaught TypeError: Intl.Segmenter is not a constructor

This javascript polyfill added using Violentmonkey is a functioning workaround :

(function() {
'use strict';
if (typeof Intl.Segmenter === 'undefined') {
Intl.Segmenter = function() {
return {
segment: (input) => [{segment: input || 'fallback'}]
};
};
}
})();

When first brought to my attention, I thought this problem was not a big deal since the person bringing this to me had a very old computer. Now that I've seen it happen on not-that-old hardware I think some kind of polyfill like the one above should be added to your code to make it compatible with older but still very common operating systems (Intl.Segmenter was declared compatible with all common browsers only since 2024)

In this time of the year I'm quite busy to work on it and make a pull request, sorry.

Thanks for the good work on this menu, it makes using Nextcloud much easier to less tech-savy people like in the instance I'm managing.

Observed Results

No response

Expected Results

No response

More informations

No response

### Environment * Custom menu version: 5.1.3 (irrelevant) * Nextcloud version: 32.0.3 (irrelevant) * Web browser and version : Firefox 115 and maybe some older versions of Chromium based browsers, etc. ### Configuration ``` { irrelevant. } ``` ### Steps to reproduce Hey there :) Found another bug, fortunately this time I could work my way around it. I manage a small nextcloud instance with users that have rather outdated or not-so-outdated hardware. Two of them are on MacOSX 10.14 since Apple does not want them to upgrade their computers, rather forcing them to buy new hardware. Thing is, the custom menu is not visible on their hardware. I could reproduce this bug in a Debian VM by installing the last Firefox 115 available : same problem, the custom menu does not appear. This is due to Intl.Segmenter being too recent for Firefox 115. [According to this](https://github.com/mdn/browser-compat-data/blob/main/javascript/builtins/Intl/Segmenter.json), it is supported only since FF 125. In older versions, it throws this error in the console : `Uncaught TypeError: Intl.Segmenter is not a constructor` This javascript polyfill added using Violentmonkey is a functioning workaround : ``` (function() { 'use strict'; if (typeof Intl.Segmenter === 'undefined') { Intl.Segmenter = function() { return { segment: (input) => [{segment: input || 'fallback'}] }; }; } })(); ``` When first brought to my attention, I thought this problem was not a big deal since the person bringing this to me had a very old computer. Now that I've seen it happen on not-that-old hardware I think some kind of polyfill like the one above should be added to your code to make it compatible with older but still very common operating systems (Intl.Segmenter was declared compatible with all common browsers only since 2024) In this time of the year I'm quite busy to work on it and make a pull request, sorry. Thanks for the good work on this menu, it makes using Nextcloud much easier to less tech-savy people like in the instance I'm managing. ### Observed Results _No response_ ### Expected Results _No response_ ### More informations _No response_

tty-13 added the

bug

label

2025-12-23 19:21:11 +01:00

deblan referenced this issue from a commit

2026-01-10 15:49:50 +01:00

fix #464: add Intl.Segmenter polyfill

deblan commented

2026-01-10 16:01:13 +01:00

Owner

Hello,

I'm not able to check the fix myself.

Can you try the version v5.1.4-rc1 please?
This release is not published on the store. You must install it from CLI (documentation).

Note: this version is not signed.

Hello, I'm not able to check the fix myself. Can you try the version [v5.1.4-rc1](https://gitnet.fr/deblan/side_menu/releases/tag/v5.1.4-rc1) please? This release is not published on the store. You must install it from CLI ([documentation](https://gitnet.fr/deblan/side_menu#installation-and-upgrade)). Note: this version is not signed.

deblan added the

WFB

label

2026-01-10 16:01:20 +01:00

tty-13 commented

2026-01-14 10:57:32 +01:00

Author

I'll try as soon as I can, I'm not available this week but as soon as I get back to my computer with the vms I'll give it a try, thanks !

deblan commented

2026-02-16 11:54:30 +01:00

Owner

@tty-13 did you try it?

tty-13 commented

2026-03-08 13:14:58 +01:00

Author

Hey.
Sorry for responding so late, haven't been much online lately.

The polyfill works on 5.1.4-rc1 ! (Firefox 115)
You can add it to main.
I'm going to use it for now since 5.2.1 doesn't seem to include the fix.

Thank you very much for this fix

Hey. Sorry for responding so late, haven't been much online lately. The polyfill works on 5.1.4-rc1 ! (Firefox 115) You can add it to main. I'm going to use it for now since 5.2.1 doesn't seem to include the fix. Thank you very much for this fix

tty-13 closed this issue

2026-03-08 13:14:58 +01:00

deblan reopened this issue

2026-03-08 14:30:23 +01:00

deblan removed the

WFB

label

2026-03-08 19:03:13 +01:00

deblan commented

2026-03-08 19:19:29 +01:00

Owner

Fixed in v5.2.2!