It doesn’t block entering comments because you need to have something selected for the plugin to work, and it doesn’t trigger in textarea boxes. At least that’s how it works for me.
Thread Starter
Li-An
(@li-an)
Well, take a look at this screenshot http://tof.canardpc.com/show/a50381a1-561c-4feb-898e-3bd7e3cdadad.html
Writing E launches a popup window for me.
Interesting. What browser and OS does this happen on?
Thread Starter
Li-An
(@li-an)
Chrome and Firefox. You can make a test here: http://jmmeyer00.alwaysdata.net/blogtest/non-classe/bogo-fr/.
Just try to type E in comment area.
You’re right. Doesn’t happen to me on my blog probably because I’m using Disqus. This is a pretty serious issue.
The code should definitely disable execution when inside entry forms.
Confirmed that this does happen on http://www.androidpolice.com when using a regular form, not Disqus (such as http://www.androidpolice.com/contact/). This is grounds for immediate plugin removal until it’s fixed (which I’ve now done).
I don’t think the latest solution, which swaps it from Shift-Enter, is ideal. People can still press Shift-Enter within textareas. Is it not possible to detect if you’re currently in a textarea and remove the listener or not react in that case?
Why people will press Shift-Enter within textarea?
I understand Shift-E combination => Capitalize letter “e”
To enter a line break as <br> instead of <p> if you have an HTML-enabled editor on, for example.
I just see it as a hack, whereas a proper workaround would be to disable Error Notification from reacting at all while in textareas.
Ok. I see.
I will try add it to the next version.
Thanks for suggestion.
