When looking at https://developer.chrome.com/release-notes/128 it seems that they were using a non-standard CSS zoom before version 128. Because Chromium based browsers are usually up-to-date quite soon, I think the version check for Chrome 128 can be removed. After all this only affects the CSS zoom property and nothing else.

When looking at https://developer.chrome.com/release-notes/128 it seems that they were using a non-standard CSS zoom before version 128. Because Chromium based browsers are usually up-to-date quite soon, I think the version check for Chrome 128 can be removed. After all this only affects the CSS zoom property and nothing else.

I think the check for browser above 128 can not be canceled, because chromium below 128 handle getBoundingClientRect/getClientRects differently from chromium above 128. We can't guarantee that all users use browser above 128.

BTW, Firefox also supports CSS zoom property in version 126+ (https://developer.mozilla.org/en-US/docs/Web/CSS/zoom), and the latest ESR version is 128.0, so the necessary version check can not be canceled.

I think the check for browser above 128 can not be canceled, because chromium below 128 handle getBoundingClientRect/getClientRects differently from chromium above 128. We can't guarantee that all users use browser above 128.

BTW, Firefox also supports CSS zoom property in version 126+ (https://developer.mozilla.org/en-US/docs/Web/CSS/zoom), and the latest ESR version is 128.0, so the necessary version check can not be canceled.

Usually the ESR version is enough for Firefox. And btw, you are not even checking the version 126 in the function. What I meant is that this bug is touching a very small area of users, which means the version check might not be necessary at all.

Usually the ESR version is enough for Firefox. And btw, you are not even checking the version 126 in the function. What I meant is that this bug is touching a very small area of users, which means the version check might not be necessary at all.

Most of Firefox's third-party forked browsers are based on the ESR version, so I chose ESR version 128 instead of CSS zoom property's minimum compatible version 126.

Some third-party chromium browsers have custom versions lower than 128, such as Supermium, centBrowser, etc. I'd like to know why we won't make the extension compatible with browsers lower than 128? The number of such user groups is not small.

As I said, the bug is quite minor and I highly doubt it's worthwhile to check against the browser version. If the latest Firefox ESR already supports the CSS zoom, that is good enough. Third-party Chromium browsers have the responsibility to keep their browsers up-to-date anyway.

So can we take a step back and remove browser version checking when Chromium fully implements MV3, and keep browser version checking until then?

So can we take a step back and remove browser version checking when Chromium fully implements MV3, and keep browser version checking until then?

Chromium has been MV3-only already for some time. Is it even related to this issue?

I have removed the browser version check.