[UI] Firefox and Chrome try to spell check DHCP snippets and node fqdn fields

[Lee Trager]

1. Firefox and Chrome try to spell check the DHCP snippet value. This results in a red line being under much of the DHCP snippet. Spell checking doesn't occur until after you've clicked in the text field containing the DHCP snippet value.
2. Firefox and Chrome try to spell check the fqdn after you click to edit it and then click cancel.

[Brendan Donegan (brendan-donegan)]

@Gavin - any particular reason this was set back to new? I think this is a fairly trivial issue (with a trivial fix) but it is an issue.

[Gavin Panella (allenap)]

@Brendan: There's a wart in the Launchpad data model: it's possible for a bug to be marked as Triaged but not have an importance set. If you're using some other mechanism to track priority then this kind of makes sense, but most of the time we don't so priority is implied by importance. I have a script that resets bugs marked as Triaged but without an importance back to New so that we get notified that we missed something, but Confirmed would probably be a better choice than New.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team