KPXC buttons only appear on valid inputs.
Sometimes invalid fields received a KPXC button.
It would be nice to be able to exclude/ignore a certain input box maybe.

The input element looks suspicious, but nothing that indicates to me why it's detected as TOTP input.
<input class="ant-input" meta="[object Object]" placeholder="http.status_code=200 error=true" type="text" value="">
I don't know of a publicly accessible web UI for this sadly :(
KeePassXC - Version 2.6.1
Revision: 9a35bba
Qt 5.15.0
Debugging mode is disabled.
Operating system: Windows 10 Version 2004
CPU architecture: x86_64
Kernel: winnt 10.0.19041
Enabled extensions:
Cryptographic libraries:
libgcrypt 1.8.5
KeePassXC - 2.6.1
KeePassXC-Browser - 1.7.1
Operating system: Win
Browser: Chromium (Edge)
So this is because the placeholder of the input contains code. IMHO that is too lax.
And then there's multiple sites that use code for the attribute values. We don't want to break the compatibility with them.
Yes, that is totally understandable. It's tricky, because even looking for word boundaries before and after code would hit this false positive 馃 I sadly have no good suggestion either.
For now I've enabled the calculation for one mutation only. But in this case there are 8 mutations, and allowing more than 3-5 would probably cause some problems. Many sites can trigger multiple calls to MutationObserver in a row, each containing more than one mutation.
@varjolintu I'm not quite sure how that relates to this issue. What calculations are you referring to?
@oliversalzburg Seems I replied to wrong issue! Sorry :D