Avoid char encoding issues and XAS

[devgeeks]

Fixes #137 Fixes #174

In order to avoid both XAS and passwords with chars that wouldn't be copied to the clipboard, instead of taking the text from the actual HTML of the value field, add the key to the field in a data-attr, then use it to fetch the value from the model and load that onto the clipboard.

Then (for the XAS), make sure to use the {{! blah }} syntax of DoT to encode the value before displaying it.

[kenmanheimer]

I'm currently failing to get a debug build of Encryptr to run, so can't test the fixes.

The thing I wanted to examine: on the dot.js site, changing {{=...}} vs {{!...} in the in-line demo, there doesn't actually change much. Assuming that escaping of characters is desired, to prevent code operation, I see that I used {{= _.escape(...) }} in similar code for the SpiderOakMobile client - see this commit. This isn't necessary if your changes prevent the problem (and/or the problem is different than I'm inferring), but since I can't test it...

Also, a test for this should go on the high-priority pendings list... )-:

[kenmanheimer]

Problem with this in desktop browser - in permissive Chrome or plain Firefox:

• In a new or existing account, create a new General entry
• Name the entry abc"def and save it
• Visit the new entry and edit it
• When I arrive in edit mode, the name has been truncated at the " to abc
• This problem happens reliably, in both the general entry's Name and Text fields, but not in the Notes field.

The problem seems to be needing to use the dot.js "encode" {{!...}} form for the label and field values, as well. I've added a commit a60a2f8 that implements that.

[devgeeks]

@kenmanheimer I take it all back. This is great. Please merge it in.