Activity log for bug #1251208

Date Who What changed Old value New value Message
2013-11-14 11:41:25 Chris Glass bug added bug
2013-11-14 11:41:25 Chris Glass attachment added A small patch to the CSS and templates to illustrate my point https://bugs.launchpad.net/bugs/1251208/+attachment/3908759/+files/diff.diff
2013-11-14 11:41:37 Chris Glass bug added subscriber Landscape Bugs
2013-11-14 11:41:51 Chris Glass description This is a subjective point, but the "maas key" field of the user prefs page should be long, in order to show the full key all the time. While testing, it happened to be several times to cut/paste only the visible portion of the key because of how my browser's mouse selection works (firefox). Having a field lenght that would show the entire key every time would prevent this from happening. It's a small thing but is very annoying to me. I did fiddle around with the CSS and the template a little, and the attached patch shows something that I think would be more user-friendly. I'm not sure if it could be merged in as is, hece the patch format. This is a subjective point, but the "maas key" field of the user prefs page should be longer, in order to show the full key all the time. While testing, it happened to be several times to cut/paste only the visible portion of the key because of how my browser's mouse selection works (firefox). Having a field lenght that would show the entire key every time would prevent this from happening. It's a small thing but is very annoying to me. I did fiddle around with the CSS and the template a little, and the attached patch shows something that I think would be more user-friendly. I'm not sure if it could be merged in as is, hece the patch format.
2013-11-14 11:41:59 Chris Glass description This is a subjective point, but the "maas key" field of the user prefs page should be longer, in order to show the full key all the time. While testing, it happened to be several times to cut/paste only the visible portion of the key because of how my browser's mouse selection works (firefox). Having a field lenght that would show the entire key every time would prevent this from happening. It's a small thing but is very annoying to me. I did fiddle around with the CSS and the template a little, and the attached patch shows something that I think would be more user-friendly. I'm not sure if it could be merged in as is, hece the patch format. This is a subjective point, but the "maas key" field of the user prefs page should be longer, in order to show the full key all the time. While testing, it happened to me several times to cut/paste only the visible portion of the key because of how my browser's mouse selection works (firefox). Having a field lenght that would show the entire key every time would prevent this from happening. It's a small thing but is very annoying to me. I did fiddle around with the CSS and the template a little, and the attached patch shows something that I think would be more user-friendly. I'm not sure if it could be merged in as is, hece the patch format.
2013-11-14 11:42:16 Chris Glass description This is a subjective point, but the "maas key" field of the user prefs page should be longer, in order to show the full key all the time. While testing, it happened to me several times to cut/paste only the visible portion of the key because of how my browser's mouse selection works (firefox). Having a field lenght that would show the entire key every time would prevent this from happening. It's a small thing but is very annoying to me. I did fiddle around with the CSS and the template a little, and the attached patch shows something that I think would be more user-friendly. I'm not sure if it could be merged in as is, hece the patch format. This is a subjective point, but the "maas key" field of the user prefs page should be longer, in order to show the full key all the time. While testing, it happened to me several times to cut/paste only the visible portion of the key because of how my browser's mouse selection works (firefox). Having a field lenght that shows the entire key every time would prevent this from happening. It's a small thing but is very annoying to me. I did fiddle around with the CSS and the template a little, and the attached patch shows something that I think would be more user-friendly. I'm not sure if it could be merged in as is, hece the patch format.
2013-11-14 11:43:10 Chris Glass attachment removed A small patch to the CSS and templates to illustrate my point https://bugs.launchpad.net/maas/+bug/1251208/+attachment/3908759/+files/diff.diff
2013-11-14 11:43:57 Chris Glass attachment added A small patch to the CSS and templates to illustrate my point https://bugs.launchpad.net/maas/+bug/1251208/+attachment/3908760/+files/diff.diff
2013-11-14 11:46:19 Raphaël Badin maas: importance Undecided Low
2013-11-14 11:46:21 Raphaël Badin maas: status New Triaged
2013-11-14 12:04:46 Chris Glass attachment added Screenshot of the applied patch https://bugs.launchpad.net/maas/+bug/1251208/+attachment/3908771/+files/maas-key-patched-screenshot.png
2015-04-24 19:12:49 Blake Rouse maas: status Triaged Fix Committed
2015-04-24 19:12:53 Blake Rouse maas: milestone 1.8.0
2015-06-22 19:33:23 Andres Rodriguez maas: status Fix Committed Fix Released