VRM changes regarding battery information on VRM not properly displayed

Q&A and troubleshooting
1

Hi @Barbara
On the same note, please, also take a look at this: Battery information on VRM not properly displayed
Many thanks in advance.

2

I’ll answer here as the quoted topic, where you’ve asked the question, is locked…

1
1321Ă—169 14.8 KB

3

Hi, unfortunately that is quite an old Firefox browser we no longer support.

Our tech team looked into it, but cannot reproduce it on the latest 3 version of Firefox or Chrome. Could you download the latest version of Firefox and see it there?

In the meantime we’re checking if you fix works for all VRM sites, but if it doesn’t, I am afraid we won’t implement the fix.

4

Probably you didn’t saw that its the ESR channel, not Release, and for the Extended Support Release, that is the current version, it’s not old…
I need ESR for certain reasons, one of them involving compatibility and support.
But nevermind, I get used…
Thanks anyway.

LE:
No offense, but boy, you’re so dependent on third party software and if something will be going south with their libraries, hold on to your pants because your entire ecosystem will go the same way…

5

Hey,

Your last addition is quite unnecessary, the part of VRM your question is about is completely made by us.

6

Then install a current version of chrome for vrm.

7

Hi Alex, copy-pasting the response from my colleague on this, also for others in the same situation:

Hi Barbara, I downloaded the exact version the user has and found the problem. It seems that firefox versions older than 121 do not support the css selector :has() by default. The user is using firefox ESR version 115 (which is the recommended for Windows 7, Windows 8, Windows 8.1, or macOS 10.12, 10.13 or 10.14). If his OS is more recent than the mentioned before I believe he can update his firefox ESR to version 128 that was released recently (4 March 2025).

If his OS is one of the mentioned before and he can’t update, which means he has to use version 115, there’s still the possibility to enable that selector that is not enabled by default. I tried to enable it and it worked.To enable the selector:

  1. On firefox ESR 115, type about:config in the search bar
  2. Search layout.css.has-selector.enabled
  3. Toggle the option
1 Like
8

Thank you, that worked!

Sorry for that comment if you took offense.

So, you see, there are systems where the users/admins want to keep the things safe and are using configs that are mature, tested and without errors. That selector is not considered mature enough and although is implemented, it’s still disabled in ESR.
A good practice is to keep things simple, compatible with at least 2-3 versions behind and not use things that are recently added.
Of course, you will add them when they are mature enough, but then, the general people pool has already migrated to them.

You’ll be surprised how many ATMs out there in the wild are still using Win7 embedded… :wink:
The same, a lot of people are using not so up to date OSes with not so up to date software.
Using only latest, cut of the edge technologies, is not so good for business as you will loose customers.

You, as company, try to mix 2 ideas that are not always miscible:

  1. Your price range for products is quite high enough for the customers to be old enough to afford those products. But old people don’t like changes and are having difficulties in learning new things.
  2. Using young people for web design leads to usage of cutting edge technology that is found only on recent hardware and technologies.

And, of course, when using middle aged programmers for developing things that want to stay on today’s trend, you’ll end up with a lot of fixes on recent releases, because old programmers lost along the way the imagination, patience and dedication for a good done job. Like a granny trying to use a smartphone… :slight_smile:

Peace and thanks! :+1:

9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.