b-form-file error messages onMouseMove
See original GitHub issueUsing b-form-file
as in the example:
<b-form-file v-model="file"></b-form-file>
<br> Selected file: {{file && file.name}}
data: {
file: null,
…
Results in console error messages in Chrome 58 (but not Firefox 53) when the mouse is moved over the file-selector area:
cperacontent.js:641 Uncaught TypeError: Cannot read property 'startContainer' of null
at Object._onMouseMove (cperacontent.js:641)
at onMouseMove (cperacontent.js:636)
In fact, you can see these errors on the https://bootstrap-vue.github.io/docs/components/form-file/ page itself, when moving the mouse over the example.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to show all error messages on the same submit click ...
So, I have a html form which I validate all inputs with some JS. When the form is empty and user clic on...
Read more >Team:Estonia TUIT/ nuxt/122a1d3
(r=i.next()).done;)l.push(r.value)}catch(t){n={error:t}}finally{try{r&&!r. ... statusCode||500},message:function(){return this.error.message||"Error"}} ...
Read more >Form File | Components
Customized, cross-browser consistent, file input control that supports single file, multiple files, and directory upload.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI, tracked down what this is related to: a Chrome plugin, Perapera Chinese Popup Dictionary, which displays Chinese dictionary info when you hover over a Chinese character. When I restarted Chrome, the plugin defaulted to disabled. After enabling the plugin again, the strange interaction occurred again and the console messages reappeared when moving the mouse over the
<b-form-file>
component. Interestingly, this interaction doesn’t occur when hovering over otherbootstrap-vue
components in my test app, including<b-button>
.Nice detective work!