What environment are you running QUnit in? (e.g., browser, Node): browser
How are you running QUnit? (e.g., script, testem, Grunt): testem (via ember-cli)
Chromium Version 66.0.3359.139
What are you trying to do?
Typing in the module filter input triggers the qunit module autocompletion but also the native browser autocomplete. This overlaps and makes filtering a specific module harder as a user has to somehow close the native autocompletion.
I'm unsure if it's expected behavior but one could possibly disable the browser autocomplete by setting the autocomplete attribute on the module filter input.
If this is ok, I can open a PR to set the autocomplete attribute to off.
Tell us about your runtime:
Chromium Version 66.0.3359.139
What are you trying to do?
Typing in the module filter input triggers the qunit module autocompletion but also the native browser autocomplete. This overlaps and makes filtering a specific module harder as a user has to somehow close the native autocompletion.
I'm unsure if it's expected behavior but one could possibly disable the browser autocomplete by setting the autocomplete attribute on the module filter input.
If this is ok, I can open a PR to set the autocomplete attribute to
off
.Thanks