Open pmonks opened 8 years ago
@pmonks two things.
Firstly, the Unique Features and Strengths input should be less than 200 characters (see the countdown). The failure mode does not seem to be very user friendly. Note that the field label should also be called 'Summary' as this is what is used in the index.
Please retry with short summary and use the longer stuff in the description field.
Secondly, what package did you use for your animated gif. We want to do something similar to this for our help docos, but have not yet worked out our workflow.
If the summary field is length limited, why does it accept additional pasted characters? Check the summary for The Fortress now - I was able to paste in the sentence I was trying to type without incident. And yeah if that field is indeed length-limited, the messaging around that (both prior to hitting the limit, and when it's hit) could do with some work.
The screen capture tool is called licecap - pretty handy! ;-)
I have changed the name of this issue. We are using a third party plugin for doing this and pasting is a limitation. Unfortunately with third party plugins we often don't find their deficiencies until we have invested a lot of time. To fix this we need to write our own plugin. This is a fairly low priority.
Usability can be improved.
Damn, licecap is not on linux, I will have to fireup my old windows laptop to use it.
Maybe silentcast would work? Note: never used it myself...
[x] Field has been renamed.
[x] Usability is clear: display of remaining characters via "## characters left"
[ ] Copy-Paste to bypass limit still "works"
If someone with access reads this, please update Issue name
When editing the summary for The Fortress, I found that keystrokes would stop being accepted by the input box after a short period of time, and there was no way to re-enable input. Chrome is up to date (
Version 52.0.2743.116 (64-bit)
), I restarted it, I rebooted the laptop - about the only thing I didn't try was a different machine (and only because I didn't have ready access to one).While it's a bit hard to pin down exactly when input is disabled, it might be related to the timing of when the preview box on the right get refreshed? Each time I tried I seemed to be able to continue typing before the first couple of refreshes of the preview box, but then after that I was hosed.
Here's a short screen cap showing the problem (it's a bit hard to make out when I'm whacking the keyboard with no effect, but believe me when I say I was mashing that thing like boiled potatoes at the end there):