registered method name still shown as Contract Interaction

Hi, I have followed the instruction in the [MM docs](https://docs.metamask.io/guide/registering-function-names.html) about registering the contract's methods name on Parity's registry on Ethereum mainnet. However, it doesn't seem to work.
To give you an example I have registered "makeOffer(uint256)" which should have "0x9a2f6474" as hex and when I check it from the register it works fine but when I interact with my contract, MM still shows "contract interaction".
This is not the only confusing part. For some other functions such as above placeBid or buyToken, from time to time MM shows "PlaceBid" or "BuyToken" and they are not even registered(I have checked the hex signature).
Is the docs/contract address out of date or is there some bugs in the current version of Metamask?
Thanks.

Start with the MM documentation on registering function names and the Parity method registry on Ethereum mainnet. Reproduce the reported behavior for makeOffer(uint256), placeBid, and buyToken, then trace how the library resolves their four-byte signatures and determine whether the registry data or MetaMask display behavior is responsible.

Written by the indexing model from the issue text.