Upgrade StorageFeedback: API key display
When an API key is generated from Settings → Security, it is displayed in the same sans typeface that the rest of the web page uses.
For some reason, the text cannot be selected (this is not actually good security practice btw, it's not the pattern that anyone else follows; I work at a network/security company and this is the industry standard, including having a copy button).
Regardless, the key is shown in a sans-serif typeface that the rest of the page uses. This particular one makes it impossible to distinguish between capital I, lowercase l, and potentially the numeral 1. It may also have letter O and numeral 0 similarity. It is better practice to show keys/tokens in monospaced fonts.
Please fix these problems, and if you are philosophically opposed to changing the first behaviour (copying), then please at least change the typeface.
For some reason, the text cannot be selected (this is not actually good security practice btw, it's not the pattern that anyone else follows; I work at a network/security company and this is the industry standard, including having a copy button).
Regardless, the key is shown in a sans-serif typeface that the rest of the page uses. This particular one makes it impossible to distinguish between capital I, lowercase l, and potentially the numeral 1. It may also have letter O and numeral 0 similarity. It is better practice to show keys/tokens in monospaced fonts.
Please fix these problems, and if you are philosophically opposed to changing the first behaviour (copying), then please at least change the typeface.
One of the times when it appeared that double-clicking or selection wasn't doing anything, I realized that it was actually selecting the navigation items in the footer. I inspected the computed styles and couldn't find anything wrong. So something is happening when the create key page turns into the page showing the key where the browser is getting confused about the DOM perhaps?