dependabot[bot] on npm_and_yarn
Bump shell-quote in /packages/t… (compare)
dependabot[bot] on npm_and_yarn
Bump minimist from 1.2.5 to 1.2… (compare)
dependabot[bot] on npm_and_yarn
Bump minimist from 1.2.5 to 1.2… (compare)
dependabot[bot] on npm_and_yarn
Bump ajv from 6.6.1 to 6.12.6 … (compare)
dependabot[bot] on npm_and_yarn
dependabot[bot] on npm_and_yarn
Bump ua-parser-js from 0.7.19 t… (compare)
sure thing -- this seems to be the root cause here:
m(Tabs, {
tabs: [
{ _id: 'sections', label: 'Sections' },
{ _id: 'settings', label: 'Theme' },
],
onChange({ options }) {
vnode.state.selectedSidebarTab = options._id;
// when changing between tabs, reset tabs to their home state
clearSettingsBeingEdited(vnode);
},
})
if i remove the onChange the problem goes away
oninput
, if you type a value in, then click to move the cursor to the start of the line, then rapidly type a lot of keys the caret eventually jumps to the end of the input. I figure it's something with oninput timing with the value
, as using onchange
instead avoids this behaviour
onChange
value
sets the input value