Feature request: allow displaying additional lines as fields

[mserajnik]

At the moment, Browserpass is hardcoded to only recognize a few specific lines that are shown as fields:

browserpass-extension/src/helpers/base.js

Lines 11 to 17 in f4fffcd

	const fieldsPrefix = {
	secret: ["secret", "password", "pass"],
	login: ["login", "username", "user"],
	openid: ["openid"],
	otp: ["otp", "totp"],
	url: ["url", "uri", "website", "site", "link", "launch"],
	};

The result ist that additional lines that have a <key>: <value> format are currently not displayed as fields:

I propose implementing a setting (by default it should probably be turned off) that also allows such lines to be parsed and then presented as fields, like in this mockup:

I would parse it in such a way that only lines that contain at least one : are recognized and that any text before the first : is interpreted as key, and any text after the first : is recognized as value. I would trim both key and value, so all variants like <key>: <value>, <key>:<value> or <key> : <value> would work.

Display-wise, as you can see from the mockup, I would allow the labels to take up more space just for these additional fields, with a maximum width and ellipsis should the key name be longer than that.

---

Use case: many services require dealing with additional fields where it would be good to be able to easily copy them to the clipboard directly from Browserpass. E.g., in the context of GitHub, that could be personal access tokens.

---

If there is interest in this, I can probably implement it and make a PR.

Question: a few other pass-compatible tools already implement this and some (like Pass for iOS) also have YAML-like multiline field support. Is this also something that would be desirable here or should support be strictly limited to single-line fields in <key>: <value> format?

[max-baz]

Thanks for the idea! I'd like to explore some specific examples of how this would be used - I can't imagine you need to copy personal access tokens all that often? I also don't really know how many people put how much of non-web-related things into pass entries (my own usage is pretty basic), I can imagine for some people this might clutter the view a lot? 🤔

There is also a long-standing request to support more of web-related fields (e.g. AWS account ID) #74, I know it's not what you refer to anyway, but just to say, that specific use-case should rather be solved by letting Browserpass fill those fields in, rather than making it easier to copy-paste them...

[mserajnik]

I'd like to explore some specific examples of how this would be used - I can't imagine you need to copy personal access tokens all that often?

True, but when I do it's always annoying having to manually select the the text instead of having an easier way to copy. Granted, on macOS I also use this Alfred workflow which works pretty well for this. But I figured, since the browser is open at all times anyway, that it might be neat to have this option in Browserpass as well.

Another use case would be static security questions that some websites use. Or the ability to quickly copy/paste bank data (I don't like to use the built-in browser payment method autofill for this).

I also don't really know how many people put how much of non-web-related things into pass entries (my own usage is pretty basic)

Maybe my use case is more rare, but I generally put any sort of credentials (not just for web services), and also some personal data that I often need (like social security number etc.) into pass. 🙂

I can imagine for some people this might clutter the view a lot?

Which is why, if this was added, I would definitely make it a setting that defaults to off.

There is also a long-standing request to support more of web-related fields (e.g. AWS account ID) #74, I know it's not what you refer to anyway, but just to say, that specific use-case should rather be solved by letting Browserpass fill those fields in, rather than making it easier to copy-paste them...

Agreed; and I guess the "static security question" use case I mentioned above would also be better solved directly for the specific sites, so disregard that as a good example for this feature request.

---

If you think the feature is out-of-scope for Browserpass, that's entirely okay with me! 😄

[max-baz]

We are generally very conservative in this project when it comes to adding config options, it forces us to spend extra time, dig down into root causes and make experience that is nice for everyone :)

Which is to say, I most certainly don't mind keeping this request open and hearing more opinions and use-cases for this feature, but if we do it, it will most likely not have a config option and will be enabled for everyone.

[mserajnik]

Fair enough; let's see if anyone else might want this then. 😃