Closed Steve-A-Orr closed 7 years ago
It was reported as to affect both Firefox and Chrome. I cannot replicate this, myself; and I thought I was a fast typer. I wonder if it has something to do with hardware. Will continue to attempt to replicate. Frankly, it is just as likely that they are just touching the last button and not actually activating it.
based upon how the code is written I see how it would be possible. A small change should eliminate the potential for it so don't worry about replicating further for now. maybe just have same tester try it when it goes live if you can
code now calls cleanSearch against the raw search at point of submission by keyboard rather than referencing the cleaned up string. This should solve for the issue. re-open if that is not the case.
This was recently reported by one of our librarians:
I gave him the "Stay calm and type slowly" advice, but promised to bring it to you for consideration. I just read issue #10 and think it could be the same...or similar. I'll ask what browsers they were using.