Allow Linked custom field to link other custom field
Feature function
Sometime a identical field might has a different ID between pages, or the ID is not human-readable. In these cases, I would like to add a custom field with human-readable name, then add a Linked field linking that custom field to that ID.
For example, given that a page with a “master key” field whose ID is mk-field:
Having multiple custom fields just to describe the single one can decrease readability of entity page. Instead of linking custom fields together maybe we should consider just adding optional label to custom fields.
Thanks, your approach is cleaner compared to mine. And it will be even better if I can set multiple names to one custom field, since I did encounter websites that use different names for the same field on different page.
This is an old feature request topic, which contains very little information about use-cases. Can you explain why you want this feature, and provide some examples of how you would use it?
I have two passwords—one for login and another for transaction. I can’t autofill transaction pwd, because it has multiple key IDs for different aspect of the webpage.
Furthermore, I have to copy every time and I feel it to be insecure that what if any privileged app read my clipboard or any webpage read it.
Of course, secure clipboard is up to the OS. But still it also makes this convenience and quicker.
I would suggest something as this, Single custom field, their names are separated by either comma, ; or |
You can already do this, if you prefix the custom field name with csv=. For example, if the field name is csv=pin,mypin,pincode, the field value will be autofilled into any input field that have the IDs pin, mypin, or pincode (not case sensitive).
You can also use a custom field name with the prefix regex=, if you want to match input field IDs using a regular expression.
