You need do define a custom attribute KPH: branch with the value 123.
The KPH name must match the name attribute of the input field (maybe use id as a fallback).
This is not how the official browser plugins are doing it and requires the user to dig up the input names using devtools once
but I consider it a cleaner solution.
KeepassXC-Browser plugins allow to associate custom attributes with custom form fields via the
KPH:
prefix.But I find the index-based association rather odd. Thus I propose to use the input
name
as lookup key when filling in the credentials.So, e.g., when you have a form like
You need do define a custom attribute
KPH: branch
with the value123
. The KPH name must match thename
attribute of the input field (maybe useid
as a fallback). This is not how the official browser plugins are doing it and requires the user to dig up the input names usingdevtools
once but I consider it a cleaner solution.