Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Extend uri-match-detection.md page to show where to find the feature #40

Closed
gene1wood opened this issue Jan 10, 2019 · 3 comments
Closed

Comments

@gene1wood
Copy link
Contributor

The uri-match-detection.md help page is very useful and detailed, explaining how the various options work. I had a tough time however finding where to access this feature.

I was able to find it in the web vault but had a lot of difficulty finding it behind that gear icon next to the URI in the credential edit page.

Would it make sense to extend this page to mention where users can find this feature?

If so I can probably PR an additional section that talks about where it can be found (maybe with some images showing where the icon is)

@kspearrin
Copy link
Member

Hi Gene,
This is already covered in the article. Is there more we can expand upon to make it clearer?

image

@gene1wood
Copy link
Contributor Author

Doh, ya I missed that sorry. Either this is just me overlooking it (which is totally possible/likely), or the page might benefit from leading off with what the feature is and where you'll find it in the various UIs, then go into what a URI is, followed by each of the URI detection model options.

I had an easy time finding the feature it in the web vault because it's revealed (you don't have to click through to get to it), but I couldn't find it in the browser extension (ended up reading through bitwarden/clients#77 to try to get a screenshot or something and eventually figured it out).

Ya, it's probably worth adding to this page just a bit since even that existing line of description only applies to the browser extension (as there is no gear options button in the web vault).

If you think this is worth it, lemme know and I'd be happy to draft a PR with an idea, or if it feels good enough already, not a problem.

@kspearrin
Copy link
Member

Since we haven't noticed an issue with others regarding this before, I say we can leave it as is for now. If a problem persists where this isn't being communicated well, we can certainly reconsider.

Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants