repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
vuejsvue | line break in textarea be excessively remove | Bug | version 2 6 11 reproduction link step to reproduce 1 set the el option to an element that contain a textarea or pre with a newline at the beginning and create a vue instance html three line break be ignore javascript new vue el app what be expect the line break be remove what be actually happen line break be not delete element restriction I think it s okay for a single line break to be ignore accord to this specification |
vuejsvue | component slot be not render inside svg foreignobject | Bug | version 2 6 11 reproduction link step to reproduce run provide fiddle there be three svg box with foreignobject 1 contain simple html tag 2 contain simple vue component 3 contain complex with slot vue component what be expect all three box should show link and input element what be actually happen third box do not show link and input element while inspect dom in chrome or in firefox you will find that element of second box and third box be identical problem be their type in chome dev console select element and tab property select input element from second box and you will find follow list object eventtarget node element htmlelement htmlinputelement input select input element from third box and you will find follow list object eventtarget node element svgelement input |
vuejsvue | ssr fail to render component inside v else of a v if with v html | Bug | version 2 6 11 reproduction link step to reproduce clone the repo run npm run dev open localhost 8080 observe console log what be expect I expect ssr to render bar bar as the client side do or I d like to get an eslint warn that this be a bad idea if that be the problem what be actually happen app vue fail to render bar component on the server instead it output and the dev server give the warning the client side render virtual dom tree be not match server render content the key part of app vue be this bar my original component be naturally long I run into this problem after change the v if line from something like foo to which seem innocuous to I finally apology for post a very possible duplicate |
vuejsvue | refinfor search upwards of inline template boundary | Bug | version 2 6 11 reproduction link step to reproduce nest a component with an inline template that have a ref in a v for what be expect component ref ref should point to the respective element what be actually happen component ref ref be a singleton array with the element reference checkinfor loop over the element ancestor up to the document root so it believe that the ref be in a loop but it actually isn t the check should stop at the component root |
vuejsvue | swap from functional to non functional component use v if do not change v data attribute | Bug | version 2 6 11 reproduction link step to reproduce click the tick box what be expect it should say blue box with a blue background colour what be actually happen it say blue box with no background colour the issue stem from the datum v attribute not be re set for the blue block div when it be swap to it be still use the datum v attribute of the child div in the functional component thus the css class styling do not apply swap from a functional component to something else be useful e g when show a simple loading bar component before swap to a more complex component |
vuejsvue | hydration fail when write like 123 value in the template and the data value be a empty string | Bug | version 2 6 11 reproduction link step to reproduce open the reproduction above and you will see a red vue warn in the console what be expect a successful hydration what be actually happen the hydration fail and the app re render absolutely this look like the problem cause by the empty text node src core vdom patch js line 646 |
vuejsvue | slot wrap in v if disappear after re render | Bug | version 2 6 11 reproduction link step to reproduce 1 jsfiddle will render both element 2 after 3s it will toggle off 3 after 3s it will toggle on 4 to see it happen again rerun the jsfiddle what be expect at step 3 the bottom slot content should re appear when togglecomponent toggle back what be actually happen the bottom slot never re appear seem to be relate to the v if on line 21 I m do this b c it s useful to have an optional slot but I don t want an extra div to appear when the slot isn t use for layout reason I m fairly new to vue so I don t know if there s a different recommend way to do this not document in the example but if parentcomponent update the slot content will re appear example code include here for perusal vue const togglecomponent datum return toggleel true create settimeout this toggleel false 3000 settimeout this toggleel true 6000 render h return this toggleel h div this slot default null const slotcomponent template const parentcomponent template component togglecomponent slotcomponent var demo new vue el demo template component parentcomponent |
vuejsvue | the string constructor can not be use as a key | Bug | version 2 6 11 reproduction link step to reproduce open the codesandbox and you ll see a warning like vue warn duplicate key detect constructor this may cause an update error click the swap button twice to swap the list in the datum trigger the error if the literal string constructor in the first list be change for any other string there be no error or warning what be expect the list should swap between the first and second list what be actually happen typeerror can not read property key of undefined this be a hard bug to track down |
vuejsvue | v once on template not work inside a v for in two case | Bug | version 2 6 10 reproduction link move from step to reproduce the repro add entry to an array cause a re render that the template intentionally display the elapse time to see which v once work and which do not what be expect all v once to never render again what be actually happen test 3 first template with a v once re render all the time workaround be to append an empty span test 5 the second template with v once still rerender workaround be to use a different tag like a span or use the v once on the parent |
vuejsvue | transition group have stutter when component update elsewhere | Bug | version 2 6 10 reproduction link step to reproduce use test1 test2 or test3 button to see transition without stutter use test4 test5 or test6 button to see transition with stutter what be expect no stutter what be actually happen while the dom be update the transition restart even though the portion update isn t a child of anything transition |
vuejsvue | error compile long string litteral many on many line | Bug | version 2 6 10 reproduction link step to reproduce just click the link and you see the error and start edit go to the second of the component and you see a red line line no 24 it say that the string literal be not correct but its because it load just a piece of it what be expect no compilation error what be actually happen a compilation error |
vuejsvue | when model and the option list change at the same time model may incorrectly set to undefined | Bug | version 2 6 10 reproduction link step to reproduce set model bind to select element and the array that iterate the option list at the same time make sure the new model value do not match any of the new option the model will be set to undefined what be expect model value to be set to 1 what be actually happen model s value set to undefined this bug only appear when model and the option change at the same and the new model value do not match any option other situation behave correctly as far as I test |
vuejsvue | infinite loop in vue template compiler | Bug | version 2 6 10 reproduction link step to reproduce git clone oguimbal vuebug git npm I npm start wait a couple of second and your compilation process will be freeze if you attach a debugger to the node process you will see the infinite loop in generatecodeframe method of vue template compiler bug what be expect I would expect the compiler not to freeze what be actually happen the compiler be freeze |
vuejsvue | vuecomponent instance retain after call vm destroy | Bug | version 2 6 10 minimal reproduction html document link load step to reproduce load the app by click the button and take a heap snapshot load unload the app multiple time by click the button end in loaded stat and take a heap snapshot search vue in the memory snapshot viewer I ve personally test this in chrome what be expect vue retain size should not increase screen shoot 2019 09 06 at 09 42 58 screen shoot 2019 09 06 at 09 43 03 what be actually happen vue retain size increase background I m use vue and turbolink together in a project where the backend serve html with vue templates inline this mean I have to create and destroy vue instance when navigate between page |
vuejsvue | scope css attribute be reuse or discard when switch between component with scoped css | Bug | version 2 6 10 reproduction link functional component regular component and slot step to reproduce after npm run serve click the toggle button and find that child have no style child and child2 component be reuse child s datum v disappear cause the style to disappear what be expect child should have a black background scope style what be actually happen child without style |
vuejsvue | nest v slot be not reactive when use abbreviate syntax v slot on component itself combine with an v if v else | Bug | version 2 6 10 reproduction link step to reproduce in my example change the value by type in the input field in the work example both value change in the not work example only the nest value change the only difference be the wrapping |
vuejsvue | dynamic v slot maybe overwite when use together with v for on same element | Bug | version 2 6 10 reproduction link step to reproduce 1 open the reproduction link 2 look at the render result what be expect js a a b b what be actually happen js a b b this be an english version of issue 10165 |
vuejsvue | v bind not update dom in client side when datum in client side be different from the server side | Bug | version 2 6 10 reproduction link step to reproduce npm install npm run dev what be expect I expect the div be like this isclient what be actually happen but now it be isclient it be not nuxt s issue I have test in my own vue ssr server without nuxt the problem be exsist still but the that project be not on the github so I paste the nuxt project s link here the core code be like this text datum return text create this text vue prototype isserver isserver isclient |
vuejsvue | wrong definition of the type asynccomponentfactory | Good First Issue | version 2 6 10 reproduction link step to reproduce 1 compare the asynccomponentfactory definition with the document handle loading state what be expect attribute component should be a promise what be actually happen asynccomponentpromise I m look forward to your solution to this issue |
vuejsvue | trigger a listener of a functional component break reactivity in safari 12 1 if iframe be on the page | Bug | version 2 6 10 reproduction link step to reproduce access the fiddle click the change button what be expect hello world should change to tada what be actually happen in late safari 12 1 on mac os nothing happen but it work as expect in other browser remove the iframe from the page make the issue go away as see here seem like maybe there s a difference in how when the late safari run the flushcallback conditionally render the iframe v if myexpression null trigger the listener inside a settimeout or call forceupdate circumvent the issue |
vuejsvue | custom directive bind differ on component vs element | Bug | version 2 6 10 reproduction link step to reproduce 1 open browser console 2 click on toggle button two time what be expect directive will emit the same console message when apply to dom element and to component on init and after click on button I m not sure what should be expect output either bind first comp bind first elem unbind first comp unbind first elem bind first comp bind first elem or bind first comp bind first elem unbind second comp unbind second elem bind first comp bind first elem what be actually happen message from the directive be the same on init but different after button have be click actual console output bind first comp bind first elem unbind first comp unbind second elem bind second comp bind first elem it seem that order in which directive be apply to dom element and component be different in my setup I have custom directive which rely on some dom attribute with configuration datum when this custom directive be bind unbound in a regular flow everything work as expect directive bind after element attribute be update however when directive be bind unbound in case of vue in place patch strategey behavior seem to be different |
vuejsvue | transition s appear hook invoke even when appear not specify falsy | Bug | version 2 5 22 reproduction link step to reproduce open the repro and note that the render page say initial appear what be expect the appear hook should not be invoke and the page should just say initial what be actually happen the appear hook be invoke even though the transition doesn t have an appear attribute and hence shouldn t be trigger on appear the same thing happen if you add appear false to the transition run into this when build some custom transition component where appear should be user control but be be invoke all the time instead |
vuejsvue | transition be erroneously run when place with bizarre sequence of sible element | Bug | version 2 5 21 reproduction link screen recording 2018 12 20 at 8 21 07 pm mov step to reproduce the fiddle contain a seemingly random sequence of element that illustrate the issue describe below 1 open the jsfiddle 2 click the change button 3 the transition play it should not try remove any of the dom element and the errant transition no long play what be expect the transition should not run css transition class should not be apply hook should not be call etc what be actually happen the transition be run css transition class be apply I come across this while build a complex form with multiple button that appear disappear base on form state I notice duplicate button in one of my unit test and find that a transition be be run even though its child s v if bind be not be change I duplicate the component and whittle it down until I arrive at the attach jsfiddle this issue appear when the follow sequence of element be align 1 a boolean entry in the vue component s datum dictionary haschange false in the jsfiddle the dom contain 2 a whose v if be bind to the boolean entry 1 2 a contain a button which modify the boolean entry 1 3 an empty element 4 a whose v if be bind to the boolean entry 1 modify by logical not in the fiddle v if haschange with this exact structure modify the boolean entry 1 will run the transition even though the transition be not bind to the boolean at all if you remove any of the above element or even reorder they the errant transition will not run which be the correct behavior why do the transition run when place with this particular set of sibling in this particular order |
vuejsvue | non break space act different than other character output nbsp in template when pass via prop | Bug | version 2 5 17 reproduction link step to reproduce 1 create a new component that accept a string prop 1 display the prop within the component s template 1 use the component in a vue application and pass a string contain a non breaking space character for the prop what be expect the output should contain a non break space what be actually happen the output show in the example provide I ve make 3 case first case be that get turn into second case be that in a long list of utf 8 character only non breaking space be escape and third when get the same list of character but retrieve it from a regular htmlelement with document queryselector test title the character aren t escape note when copy the non break space character it might turn into a regular space in the clipboard therefor use keyboard entry method to make sure how to insert the character |
vuejsvue | use multiple select with v model and bound and unbound value cause value override | Bug | version 2 5 17 reproduction link step to reproduce change first select to some then change newly display select you will see that val2 be be set to the bind val from the val1 select instead of it s own value you can change the first select to use the number modifier on the v model and exchange the bind number value for string to fix this issue at least for this very specific desire effect you can fix the problem by either use v bind value on all value or by use non bind value on all value but as far as I can tell if you mix they then it will cause this override bug what be expect different value for each variable what be actually happen second variable be be overwrite with the first s value this be post discuss in the discord chat |
vuejsvue | v once for component tag doesn t work in v for | Bug | version 2 5 16 reproduction link step to reproduce run code and watch what be expect yay yay value should not change to hell naw in 3 second what be actually happen yay yay value be change in to hell naw in 3 second wait 3 second behavior be not consistent component tag in v for should not change comp comp |
vuejsvue | and v show trigger move transition on enter | Bug | version 2 5 16 reproduction link step to reproduce 1 open the fiddle 2 click the toggle button 3 watch the move transition trigger on enter what be expect just like with v if move transition should not be trigger on enter note that it be already not trigger on leave what be actually happen I haven t check in the source yet but I m guess that since element with display none still technically have coordinate domrect x 0 y 0 width 0 height 0 top 0 right 0 bottom 0 leave 0 the move transition be trigger on enter I m not sure why it wouldn t also occur on leave though this may be connect to 5800 also special thank to rachelnabor for find this bug |
vuejsvue | rerender while change affect only sible element | Bug | version 2 5 2 reproduction link step to reproduce please open codepen example and type something into input what be expect input should not lose focus what be actually happen input rerender and lose focus happen only if there be such conditional element exist before and after input workaround be to use v show instead of v if in such case |
vuejsvue | provide prop be not inject into functional component | Bug | version 2 3 3 reproduction link step to reproduce I create a minimal reproduction of the behavior I be try to test the example just need jsx to work what be expect the property pass down from parent should show up in ctx injection what be actually happen ctx injection exist but remain empty the property be not be pass down to the functional component context |
vuejsvue | v on change randomly fail on range input bind on a compute property | Bug | vue js version 2 1 10 reproduction link step to reproduce the above jsbin contain a slider range that log the value of a compute property it be bind to sliderradius when it change v on change log log be a declare function what be expect I would expect that each time the slider change the prop be log in the console what be actually happen two different scenario you drag and release the slider handler aka thumb the prop be always log in the console I e the change handler fire properly all the time you directly click where you want the handler to get to the prop isn t log all the time I e the change handler fail about in 3 out of 5 occasion see the animate gif below use the provide jsbin record on google chrome osx the same happen on safari think vuerangechangeerror gif thank you |
vuejsvue | compiler sfc not compatible with prettier v3 | Bug | version 2 7 14 reproduction link I think it s not necessary as it s obvious in source code step to reproduce install prettier v3 in a project depend on vue compiler sfc v2 what be expect no error what be actually happen fail in compile template I find compiler sfc try to format code with api of pretty but format of pretty become async in v3 and it return a promise instead of string l179 |
vuejsvue | fix correctly update style | Bug | fix 12901 what kind of change do this pr introduce check at least one x bugfix feature code style update refactor build relate change other please describe do this pr introduce a break change check one yes no if yes please describe the impact and migration path for exist application the pr fulfill these requirement it s submit to the main branch for v2 x or to a previous version branch when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number all test be pass development setup new update test be include if add a new feature the pr s description include a convincing reason for add this feature to avoid waste your time it s good to open a suggestion issue first and wait for approval before work on it other information |
vuejsvue | bind style merge not as expect | Bug | version 2 7 14 reproduction link codesandbox io step to reproduce click mstyle button twice what be expect show red border right and blue border bottom what be actually happen only show red border right be not similar as setattribute but vue3 be similar like setattribute be this a bug |
vuejsvue | watcher depend on current route re evaluate after unmount | Bug | version 2 7 8 reproduction link codesandbox io step to reproduce have a watcher with a dependency on the current route unmount the component what be expect no watcher effect be call what be actually happen watcher effect be call look like it s the same issue as for vue 3 |
vuejsvue | kabab case component doesn t work when I type same name but camelcase ref | Bug | version 2 7 7 reproduction link github com step to reproduce 1 clone the repo 2 run pnpm I 3 run pnpm dev what be expect kebab case component can be render what be actually happen kebab case component can t be render but when I delete ref sentence it work be it a bug it can work in vue3 it also can work in vue2 6 vue composition api |
vuejsvue | vue 2 7 injection symbol pinia not find | Bug | reproduction step to reproduce the bug open the reproduction link and see the terminal of devtool expect behavior should not throw any error actual behavior vue warn injection symbol pinia not find additional information doesn t meet this issue with vue 2 6 vue composition api |
vuejsvue | fix compiler sfc support more indent lang | Bug | what kind of change do this pr introduce check at least one x bugfix feature code style update refactor build relate change other please describe do this pr introduce a break change check one yes x no if yes please describe the impact and migration path for exist application the pr fulfill these requirement it s submit to the dev branch for v2 x or to a previous version branch not the master branch when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number x all test be pass development setup new update test be include if add a new feature the pr s description include a convincing reason for add this feature to avoid waste your time it s good to open a suggestion issue first and wait for approval before work on it other information stylus style with indentation be lose after compilation javascript |
vuejsvue | prop be not reactive in 2 7 0 beta 2 | Bug | version 2 7 0 beta 2 reproduction link stackblitz com step to reproduce ts import definecomponent isreactive toref from vue export default definecomponent prop foo string setup prop console log prop isreactive prop toref expect a reactive object but receive a plain one console log toref prop foo what be expect prop be reactive what be actually happen prop be not reactive p s createapp doesn t exist now will it be add in the final version of 2 7 |
vuejsvue | fix type async component type | Bug | what kind of change do this pr introduce check at least one x bugfix feature code style update refactor build relate change other please describe do this pr introduce a break change check one yes no x not sure if this be consider a break change if yes please describe the impact and migration path for exist application the pr fulfill these requirement x it s submit to the dev branch for v2 x or to a previous version branch not the master branch x when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number x all test be pass development setup x new update test be include other information look at this codeexample ts import asynccomponent component from vue const a asynccomponent component new promise re rej re const b asynccomponent component new promise re rej re the first example be like in the doc handle loading state and the second example should not work I also look at the implementation and I think this would not work the type be currently like such that the first example throw a type error and the second throw no error this pr fix that |
vuejsvue | compute field for name slot stop work if I add watcher to they | Bug | version 2 6 11 reproduction link step to reproduce 1 click the button to see that the compute field work 2 uncomment the watcher 3 click button again and notice that compute field don t work and the watcher be never trigger what be expect compute field work and watcher be trigger what be actually happen compute field don t work and watcher be never trigger code app vue vue helloworld vue vue edit I update the code example to make it easy |
vuejsvue | slot be reuse with v if v else | Bug | version 2 6 12 reproduction link step to reproduce click the switch button it will switch between two component with slot and without slot the component without slot should not appear the slot pass to the component with slot what be expect should display the fallback slot what be actually happen display the previous slot |
vuejsvue | fix ssr avoid miss file in manif | Bug | what kind of change do this pr introduce check at least one x bugfix feature code style update refactor build relate change other please describe do this pr introduce a break change check one yes x no if yes please describe the impact and migration path for exist application the pr fulfill these requirement x it s submit to the dev branch for v2 x or to a previous version branch not the master branch when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number all test be pass development setup new update test be include if add a new feature the pr s description include a convincing reason for add this feature to avoid waste your time it s good to open a suggestion issue first and wait for approval before work on it other information reproduction when I run npm run build win actually file vue ssr client manifest json module any contain 1 then ts node serve serve ts the serve start when visit any web ex localhost 8000 it will shows error can not read property replaceall of undefined |
vuejsvue | unknown custom element | Bug | version 2 6 11 reproduction link step to reproduce open the console in the provide jsfiddle or run vue config gettagnamespace foreignobject what be expect vue config gettagnamespace foreignobject should return svg what be actually happen it return undefine this cause a warning unknown custom element when test such component use vue test util this be cause by l29 it should be foreignobject with lowercase o here because of the makemap implementation to avoid such bug in the future even well fix l113 should be map expectslowercase list I tolowercase list I true |
vuejsvue | vue server renderer inheritattrs false doesn t work properly | Bug | version 2 6 11 reproduction link step to reproduce clone the repo npm install npm run test or javascript step 1 create a vue instance const vue require vue const appcard template appcardprop appcardprop prop appcardprop const playercard template component appcard inheritattrs false const app new vue template component playercard step 2 create a renderer const renderer require vue server renderer createrenderer step 3 render the vue instance to html renderer rendertostre app err html if err throw err console log html appcardprop appcardprop value html attribute app card prop must be miss what be expect html appcardprop appcardprop value what be actually happen html appcardprop appcardprop value this bug happen when I use component with inheritattrs false which use another component on top level of section or render function I want to pass prop to inner component with v bind attrs and inheritattrs false it pass prop inside but still add attribute to html element I notice that this bug doesn t occur in next case if I set inheritattrs false on inner component appcard of code section if top level of template or render function be not a component e g simple div or span relate |
vuejsvue | fix keep alive should not cache destroy instance | null | what kind of change do this pr introduce check at least one x bugfix feature code style update refactor build relate change other please describe do this pr introduce a break change check one yes x no if yes please describe the impact and migration path for exist application the pr fulfill these requirement x it s submit to the dev branch for v2 x or to a previous version branch not the master branch when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number x all test be pass development setup x new update test be include if add a new feature the pr s description include a convincing reason for add this feature to avoid waste your time it s good to open a suggestion issue first and wait for approval before work on it other information reproduce link after keep alive child component destroy itself component instance be be create every time when it re activate please check reproduce link and test code |
vuejsvue | fix core fix samevnode for async component | Bug | I find and fix a vdom bug relate to async component and ssr I originally notice this bug on my closed project use nuxt the minimal reproduction code be include in test phenomenon throw when hydrated pende async component be patch by v if false node version 2 6 11 cause 1 v if false node be represent by comment node 2 samevnode return true when asyncplaceholder and comment be compare 3 patchvnode execute for asyncplaceholder and comment 4 comment doesn t have asyncfactory but asyncfactory resolve be access fix fix samevnode to return false when asyncplaceholder and comment be compare what kind of change do this pr introduce check at least one x bugfix feature code style update refactor build relate change other please describe do this pr introduce a break change check one yes x no if yes please describe the impact and migration path for exist application the pr fulfill these requirement x it s submit to the dev branch for v2 x or to a previous version branch not the master branch x when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number x all test be pass development setup x new update test be include if add a new feature the pr s description include x a convincing reason for add this feature to avoid waste your time it s good to open a suggestion issue first and wait for approval before work on it other information |
vuejsvue | with whitespace condense all nbsp even meaningful be convert to space | Bug | version 2 6 11 reproduction link step to reproduce run example js in node alternative step detailed explanation 1 setup vue template compiler with whitespace condense it be default for vue cli 2 render template with entity e g a b 3 inspect template for actual non break space character what be expect entity render as non break space character example js output should contain whitespace condense code nbsp find what be actually happen entity be render as plain space example js output contain whitespace condense code nbsp not find the whitespace be strip by this compiler code js if inpre whitespaceoption condense condense consecutive whitespace into single space text text replace whitespacere and s be replace by xa0 s with entity decoder early relate issue be suggestion narrow whitespacere regexp like t r n g |
vuejsvue | problem with v bind class in microsoft edge for component | Bug | version 2 6 10 reproduction link step to reproduce open codepen example there be 3 component test x on the page which set text color and background each label tell about text color and background chrome everything work as expect edge 18 1st and 3rd label have incorrect color what be expect 1 red text on yellow bg 2 red on gray 3 black on yellow what be actually happen 1 black on gray 2 red on gray 3 black on gray |
vuejsvue | multiple argument in custom event with a modifier be not pass to handler | Bug | version 2 6 10 reproduction link step to reproduce add a modifier to one of the event listener e g emission once what be expect that all argument will be pass to the function what be actually happen only the first argument be pass my guess be that it lie in the template compiler which create a function event and call the handler with event instead of argument |
vuejsvue | unexpected comma in the function declaration | Bug | version 2 6 10 reproduction link l3296 l3296 step to reproduce see the link l3296 what be expect function createcomponentinstanceforvnode vnode we know it s mountedcomponentvnode but flow doesn t parent activeinstance in lifecycle state what be actually happen function createcomponentinstanceforvnode vnode we know it s mountedcomponentvnode but flow doesn t parent activeinstance in lifecycle state I ve get an error when try to add the vue esm browser js file into a bundle use systemj builder |
vuejsvue | ssr textarea domprop keep falsy value | Bug | version 2 6 10 reproduction link step to reproduce view page source what be expect html what be actually happen html null similar to 9231 repro in vue test ssr ssr string spec js js it falsy domprop value do rendervmwithoption render h return h div h textarea domprop value null result expect result tocontain do relevant vuetify code l86 l92 l357 l361 |
vuejsvue | vue server renderer directive not apply to import component | Bug | what problem do this feature solve currently ssr directive be not apply to use sub component but only to html tag and element reproduction js step 1 create a vue instance const vue require vue const test template this should be red const app new vue template this be red component test const makere node dir const style node data style node datum style if array isarray style style push backgroundcolor red else style backgroundcolor red step 2 create a renderer const renderer require vue server renderer createrenderer directive makere step 3 render the vue instance to html renderer rendertostre app err html if err throw err console log html this should be red this be red but should include red background color style for the first div as well relate |
vuejsvue | render async load component be cause attrs change | Bug | version 2 6 10 reproduction link step to reproduce 1 create component with render function which can render another component after time 2 render component after promise resolution timeout be cause render twice and change of attrs if child component have any prop with key equal to attr 3 comment prop in targetcomponent and reload page 4 all attrs be fine again what be expect render function be call once and attrs of component be not change what be actually happen render be call twice and attrs which have key same as prop of child component be remove I create on my project custom loader component which have to handle loading of lazy load component and networking error because I can t use handle loading state in my case this bug can be ommite by not add download component to reactivity outside datum as variable |
vuejsvue | prop validator fail to generate validation error message when use symbol | Bug | version 2 6 10 reproduction link step to reproduce pass a symbol as the value of a component prop which expect another type what be expect the console should show the validation error message what be actually happen the prop validator try to build an validation error message it fail with typeerror can not convert a symbol value to a string |
vuejsvue | with whitespace condense element contain only nbsp and space be condense into empty tag | Bug | version 4 0 0 rc 1 reproduction link environment info environment info system os macos 10 14 6 cpu 4 x64 intel r core tm i5 7360u cpu 2 30ghz binary node 10 15 3 usr local bin node yarn 1 17 3 npm global bin yarn npm 6 11 3 npm global bin npm browser chrome 76 0 3809 132 firefox 68 0 2 safari 12 1 2 npmpackage vue babel helper vue jsx merge prop 1 0 0 vue babel plugin transform vue jsx 1 0 0 vue babel preset app 4 0 0 rc 1 vue babel preset jsx 1 1 0 vue babel sugar functional vue 1 0 0 vue babel sugar inject h 1 0 0 vue babel sugar v model 1 0 0 vue babel sugar v on 1 1 0 vue cli overlay 4 0 0 rc 1 vue cli plugin babel 4 0 0 rc 1 4 0 0 rc 1 vue cli plugin eslint 4 0 0 rc 1 4 0 0 rc 1 vue cli service 4 0 0 rc 1 4 0 0 rc 1 vue cli share util 4 0 0 rc 1 vue component compiler util 3 0 0 vue preload webpack plugin 1 1 1 vue web component wrapper 1 2 0 eslint plugin vue 5 0 0 5 2 3 vue 2 6 10 2 6 10 vue eslint parser 5 0 0 vue hot reload api 2 3 3 vue loader 15 7 1 vue style loader 4 1 2 vue template compiler 2 6 10 2 6 10 vue template es2015 compiler 1 9 1 npmglobalpackage vue cli 4 0 0 rc 1 step to reproduce clone the repo npm install npm run serve what be expect the template contain a span contain a character this span have a red background thus you should see a small red box on the page what be actually happen the in the template be be ignore and convert into a normal space which mean the span element be not display I can not replicate this bug in a plain vue jsfiddle nor a project use vue loader without vue cli thus I think something in vue cli may be the culprit rather than vue template compiler or vue itself |
vuejsvue | datum property not find and or incorrectly type in typescript 3 6 2 | Bug | version 2 6 10 reproduction link be aware that jsfiddle do not show typescript compiler error step to reproduce use typescript 3 6 1 beta currently stable at 3 6 2 have at least one prop correctly type all your method use a non string data property in your component option what be expect normal behavior the datum property be correctly type and find on the instance what be actually happen error arise because in method the datum property be not find on the component type in watch the datum property be type string watchoptionswithhandler watchhandler in compute the datum property be type any computedoption |
vuejsvue | nest async component pass as slot be not render in ssr | Bug | version 2 6 10 reproduction link step to reproduce when the codesandbox start up it should run the npm start script if it doesn t open a bash terminal and run npm start to see the html generate from ssr you can also take a look at the component in the src folder to see how they be configure what be expect expect the html for the nest async component call somecomponent to be render during ssr html leave somecomponent with value first right somecomponent with value second what be actually happen the html for the nest async component call somecomponent be not render during ssr only the html for the outer async component call grid be render html leave right I have an app that be compose of many async component some of these component have name slot I be try to build a render function that will accept a config object to render these component in various setup for example an async component set to a name slot of another async component I notice that if I nest async component within another the html for the async component do not render during ssr the codesandbox be simplify scenario of this |
vuejsvue | default slot content should not be evaluate when the parent be provide it | Bug | version 2 6 10 reproduction link step to reproduce in the child vue we have a slot with a default slot content in the parent vue we override the default content of the child what be expect imo the content of the slot in child component should not be evaluate since the content provide from the parent will be use what be actually happen the content of the parent it render which be what I expect the default content of the child vue it s evaluate even if it not render that s why you see in the console can not read property length of null maybe that s not a bug and instead it s the intentional behavior but it doesn t make sense to I to evaluate something that will not render |
vuejsvue | scope slot warn when use inside of dynamic component on regular element | Bug | version 2 6 10 reproduction link step to reproduce when I use dom template parse caveat to add a component e g I can t use scope slot slotprop without receive a warning in the console I would like to use it this way html slotprop slotprop test what be expect no warning what be actually happen I get the follow warning in the console vue warn error compile template v slot can only be use on component or |
vuejsvue | attribute list under isbooleanattr be alter under v pre attribute tag | Bug | version 2 6 10 reproduction link step to reproduce in a v pre tag or child use an attribute list under the isbooleanattr list in src platform web util attrs js what be expect the attribute value be unchanged what be actually happen the attribute value be change e g open have the value to set to open when work with mathml we need to use the open attribute |
vuejsvue | bug about keep alive and click native cause repeat attach event handler | Bug | version 2 6 10 reproduction link step to reproduce 1 click show hide button to hide button add 1 2 click show hide button to show button add 1 3 click add 1 what be expect repeat step 1 and step 2 click the add 1 to add 1 to the number what be actually happen repeat step 1 and step 2 click the add 1 to add n repeat time to the number 5 0 window not 10 0 win64 x64 applewebkit 537 36 khtml like gecko chrome 74 0 3729 169 safari 537 36 |
vuejsvue | memory leak with component with input with v model | Bug | version 2 6 10 reproduction html document go to home go to about screen shoot 2019 05 09 at 18 59 07 step to reproduce go to the about page type in the input leave the page collect garbage and take a snapshot with devtool what be expect vuecomponent count should be stable what be actually happen vuecomponent count keep increase seem to be relate to type in the input |
vuejsvue | doesn t destroy cache component after when max be 1 | Bug | version 2 6 10 reproduction link step to reproduce 1 open dev tool to see console 2 cycle through the route 3 view console and observe lifecycle hook log what be expect I d expect once the max cache be reach in the example case of 1 the component that get prune also get destroy in the documentation keep alive it state emphasis mine max the maximum number of component instance to cache once this number be reach the cache component instance that be least recently access will be destroy before create a new instance what be actually happen the prune component be never destroy it s just remove from the cache in the example the beforedestroy hook be never call related code l37 l49 |
vuejsvue | fix keep alive cache what be really need not the whole vnode | Bug | cache what be really need not the whole vnode datum it also fix 9842 fix 2549 fix 9972 what kind of change do this pr introduce check at least one bugfix feature code style update x refactor build relate change other please describe do this pr introduce a break change check one yes x no if yes please describe the impact and migration path for exist application the pr fulfill these requirement x it s submit to the dev branch for v2 x or to a previous version branch not the master branch when resolve a specific issue it s reference in the pr s title e g fix xxx xxx where xxx be the issue number all test be pass development setup new update test be include if add a new feature the pr s description include a convincing reason for add this feature to avoid waste your time it s good to open a suggestion issue first and wait for approval before work on it other information |
vuejsvue | build project with vue cli 2 if some function name functionclickhandle and bind with click functionclickhandle it will run automatically | Bug | version 2 5 9 reproduction link step to reproduce 1 clone my github project 2 npm I npm run dev 3 I look like be require something happend window alert 1i be big boss window alert 2i be big boss because it run s automatically 4 but window alert item click change do not what be expect I just want to report what be actually happen run automatically vue version 2 5 2 one day I maintain an old project something just happend my web page always redirect to anothoer page until I change the function name functionclickhandle with itemclick because functionclickhandle have some judgment inside and run automatically |
vuejsvue | memory leak when use transition and keep alive | Bug | version 2 6 10 reproduction link step to reproduce I write a demo html demo the debug process be as follow 1 click collect garbage and take heap snapshot snapshot 1 2 click the route button on the left 10 time then click collect garbage and take heap snapshot snapshot 2 3 click the route button on the left 10 time then click collect garbage and take heap snapshot snapshot 3 the generate snapshot be as follow snapshot 1 snapshot 2 snapshot 3 after click 100 time vuecomponent be not be recycle be this a bug what be expect why be this happen be this a bug what be actually happen component will not be clear when switch component |
vuejsvue | error use multiple dynamic slot name invalid dynamic argument expression | Bug | version 2 6 10 reproduction link step to reproduce 1 clone this repo 2 run npm install 3 run npm run serve what be expect multiple dynamic slot name should work as expect what be actually happen the follow error be throw invalid dynamic argument expression attribute name can not contain space quote or headerslot header slot default slot default slot |
vuejsvue | default scope slot be not present under data scopedslot object in functional component | Bug | version 2 6 8 reproduction link step to reproduce check console log what be expect I expect data scopedslot to always be the same as its mirror object scopedslot in functional component context what be actually happen default scope slot function be undefined in data scopedslot but not in context scopedslot object unless I explicitly use default scope slot the template vue |
vuejsvue | different behavior of arrow function and function | Bug | version 2 6 8 reproduction link step to reproduce html price e target value compile js with this return c input domprop value price on input e price e target value html this will not be work compile js with this return c input domprop value price on input function event function f e price e target value what be expect can be work what be actually happen this will not be work |
vuejsvue | slot prop in render function be not sync | Bug | version 2 6 8 reproduction link step to reproduce first number picker be declare in container two second number picker be declare by footer slot change number picker the value of the first number picker would be change but the value of the second number picker would not be change if add slot content in container two js code line 59 61 the value of the second number picker will be change what be expect there be two situation if this code be correct without line 59 61 both number value should be change when picker change if this code be wrong should add line 59 61 it should have error message or even not render slot what be actually happen the value of the second number picker should be change or error message should be show or even not render slot |
vuejsvue | runtime exception performance be not define with v2 6 9 | Bug | version 2 6 8 reproduction link step to reproduce it be throw from the vue dist vue js file of the late version I be currently try to isolate it yet it seem connect with the new code add recently will add more step asap if you still don t observe it 1 replicate with this repo 2 clone it 3 npm I 4 npm test no error 4 npm update vue 5 npm test referenceerror performance be not define greeting plaman what be expect no error observe what be actually happen an error be observe |
vuejsvue | default slot without the new template syntax will not reevaluate v if | Bug | version 2 6 4 reproduction lin step to reproduce use the toggle button the syntax use in line 29 seem to not work as expect what be expect all 3 paragraph should always print the same text what be actually happen the default slot without the new template syntax will only rerender once and then stay the same I m not sure if the syntax for default slot be now still to be use that way or if we always need to use a template now but it work with 2 6 0 to 2 6 3 and then stop work in 2 6 4 edit update reproduction close that slot tag |
vuejsvue | camelcase prop bind through an object take precedence over a kebab case specific prop | Bug | version 2 6 8 reproduction link step to reproduce the repro show the issue directly what be expect I want to know what take precedence when something be bind use v bind vs set explicitly as a prop I would expect this to always be one or the other or to be resolve in order of declaration as when merge object in js boundprop specificprop what be actually happen the precedence be determine base on whether a prop have multiple word duplicate key be set by the object when they be declare in dash case and set by the prop attribute if they be camelcase or a single word this can be make consistent by declare multiword prop use camelcase but that s against the recommendation in the styleguide which suggest use dash case for multiword prop inside template prop name casing strongly recommend I run into this when an undefined value bind to a parent be override the same value explicitly set in the child but it wasn t happen consistently depend on what the name of the prop be |
vuejsvue | transition component animate when wrapper be replace | Bug | version 2 6 8 reproduction link step to reproduce press the change screen button to toggle between screen 1 and screen 2 what be expect nothing should fade and nothing should be log to console because the v if within the be always true what be actually happen on each press b fade in again and enter b custom component get log to the console I ve include a as well as b to show that the bug only occur when use a custom component with a and a use the directly and doesn t exhibit the buggy behavior nb I ve also notice that if the custom component be switch to be functional instead then it begin work correctly the same as a so it appear to only be reproducible when use a custom component and even though this be what the doc recommend reusable transition or it s possible that I ve misunderstood the expect behavior of a inside of a keyed or otherwise newly appear component in which case there s still a bug because in that case a and b should both be fade and log to console though that seem weird to I the isn t appear true so the fact that its parent be newly appear shouldn t affect it |
vuejsvue | type normalizedscopedslot for scopedslot on rendercontext | Bug | version 2 6 8 reproduction link step to reproduce yarn install yarn serve what be expect yarn serve without error what be actually happen type error argument of type functional boolean render h createelement ctx rendercontext string true vnode scopedslotreturnarray be not assignable to parameter of type componentoption defaultmethod defaultcompute propsdefinition record object literal may only specify know property and functional do not exist in type componentoption defaultmethod defaultcompute propsdefinition record 15 16 export default vue extend 17 functional true 18 render h ctx 19 const child ctx scopedslot default ctx scopedslot default 20 return child h version typescript 3 3 3333 pr 9563 introduce normalizedscopedslot type but rendercontext type for functional component still use scopedslot key string scopedslot be it expect |
vuejsvue | deep object as dynamic argument in custom directive rfc 0003 | Bug | version 2 6 7 reproduction link step to reproduce create custom directive with a dynamic argument v test deep arg value what be expect it should get the value from path deep arg what be actually happen inside the bind object of a custom directive arg key have value deep |
vuejsvue | component create with async component factory break on route change | Bug | version 2 6 7 reproduction link step to reproduce 1 open 2 immediately before the async component be resolve within 7 sec click on the some page link 3 click on the home link before 7 be elapse what be expect the asyncready component should render after 7 second what be actually happen the asyncloade component be show forever the problem be that the currentrenderinginstance be home after render the somepage route the initial home instance which be store as the owner of the factory be destroy as soon as the factory call forcerender trigger forceupdate on the owner do nothing because the old home instance already be destroy and a new one be create when navigate back to home this be problematic on very slow connection when user click a link before all dynamic component be resolve or in case of automatic redirect which be trigger immediately after a page be load after check auth for example see l58 l74 |
vuejsvue | vue config errorhandler call twice when I return a reject promise from a handler of a component event | Bug | version 2 6 6 reproduction link step to reproduce the problem seem to happen when I handle an event emit from a component and return a reject promise to see the problem in action open the codepen link click the button and you will see in the console two log of the same error which mean the vue config errorhandler be call twice what be expect I expect the errrorhandler call once what be actually happen the errorhandler function be call twice |
vuejsvue | value inside v slot in a v for win t update | Bug | version 2 6 0 reproduction link jsfiddle step to reproduce you can see the problem on a deploy version of here you run into a problem like that if 1 you have a v slot inside a v for and in that v slot you render an item from v for 2 you update whole array that drive the v for what be expect render item in v for should behave in a same way as render item in v for inside a v slot it should be re render when the whole array drive the v for change I d expect no change in behavior from vue 2 5 22 you can see how it behave on the same code with vue 2 5 22 I have deploy same code with downgraded vue version here what be actually happen the item inside v for in a v slot be not re render l6 I know that the issue can be resolve by provide proper v key to the v for the confusing part though be that the even without the v key this line be update l4 but this line be not l6 if that s not a bug but something I don t understand about scope slot it might be good to add some information about that in some vue reactivity gotchas I wonder why it bite I give a change from 2 5 2 6 should not be break |
vuejsvue | v on dynamic argument doesn t work with native modifier | Bug | version 2 6 0 reproduction link step to reproduce I make a simple button component which do not emit any event in the app there be three instance of it with the click native event bind in different way you can see the first button component which be bind with click native work and increase the counter but the rest which use v on and the new conditional bind syntax do not I think it might have be some limitation of native event but this also happen with other modifier like keydown somekey what be expect the event should be bind and all the button should work what be actually happen the button do not work the event be not bind only the first button actually get a listener attach when I inspect they with chrome s devtool |
vuejsvue | 2 6 beta regression component without slot re render when parent update | Bug | version 2 6 0 beta 3 reproduction link step to reproduce click the root button what be expect update root should be log what be actually happen update childcomponent be also log if you add v slot default it work as expect vue 2 5 22 also work correctly |
vuejsvue | in ie 11 the first input event on a text input be block if placeholder be set and the model be initialise | Bug | version 2 5 22 reproduction link step to reproduce 1 open in ie 11 2 enter a single character in the text input just after hello vue 3 model will not be update on the first character input but will be on subsequent input note to reproduce a second time you will need to refresh the page what be expect when a single character be enter the model should update what be actually happen the input event be block and the model do not update until a second character be enter I believe it could be relate to a previous fix for an issue that ie11 be fire an input event when the placeholder be set perhaps it should check if the value be set first before block the initial event many thank declan |
vuejsvue | vbind style do not work with zindex | Bug | version 2 5 22 reproduction link step to reproduce give a very simple component zindex be not bind to style what be expect bind zindex do not get kebab case like maxwidth and minwidth I expect it to work the same way pass z index work as expect what be actually happen the zindex variable be ignore entirely I be create an alert style box that need a high z index to appear on top of other element on the page |
vuejsvue | transition not trigger appear when use as the root of a component with appear attr | Bug | version 2 5 22 reproduction link step to reproduce open repro click on the show button and note that animate on enter text appear what be expect to see a text animate on appear which have to be add by appear hook what be actually happen the enter hook be call instead of appear important be that transition be move to separate component also everything work as expect if transition isn t a root element in a separate component or the component be functional |
vuejsvue | v if event handler | null | version 2 6 0 beta 1 reproduction link step to reproduce click on click I what be expect demo with v2 5 22 show the expect behavior the dropdown component should not be able to handle a click event which be suppose to create it what be actually happen the dropdown be automatically close because it handle the click event |
vuejsvue | v model s value not in attrs if value not define as a prop | Bug | note this issue only refer to v model for component and be not consider v model on dom element there be a discussion which include this unexpected behavior in 6216 and also a pr 6327 that try to fix that but those also include be able to pass through v model to dom element which be not the case with this issue version 2 5 22 reproduction link step to reproduce use v model on a component that doesn t have value define in its prop what be expect value be add to component s instance attrs what be actually happen value be not add to component s instance attrs because of that when wrap a component and pass through the prop and event handler use v bind attrs v on listener v model will not be completely pass through and will require explicitly define value in wrapping component s prop and pass it use value value to the wrap component see the link sandbox |
vuejsvue | class bind not update on client after use isserver with boolean value | Bug | version 2 5 21 reproduction link step to reproduce code sandbox will illustrate the issue may take a few second to load notice how isactive print true yet the class isn t bind what be expect class to bind class attribute class nav link active and cause nav link to turn red what be actually happen not bind class and make nav link red |
vuejsvue | ssr style bind keep falsy value | Bug | version 2 5 21 reproduction link I know minimal repro below step to reproduce view page source what be expect html what be actually happen html reproduce in vue test ssr ssr string spec js then run npm run test ssr js it falsy style value do rendervmwithoption template datum style opacity 0 color null result expect result tocontain |
vuejsvue | provide value in mixin be not accessible | Bug | version 2 5 21 reproduction link open the link and see the error message in dev console step to reproduce create two mixin with a provide object use symbol as it s key field then assign these mixin to a component what be expect the child component can access two provide object without any error what be actually happen the child component can only access the last provide object while the first one be undefined diving into the source code the reason of this issue be that vue use object key to iterate over the provide object while merge mixin however object key win t return symbol key see the code l51 maybe we should use for in loop which will iterate through symbol key correctly |
vuejsvue | vue do not correctly dedupe global mixin global mixine lifecycle hook be call twice | Bug | version 2 5 21 reproduction link step to reproduce goto the minimal reproduction link or simply add this to test unit feature option mixin spec js js it should not mix global mixine lifecycle hook twice const spy jasmine createspy global mix in lifecycle hook vue mixin create spy const mixin vue extend const child vue extend mixin mixin create const vm new child expect spy call count tobe 1 what be expect spy to be call once what be actually happen spy be call twice when use vue class component it s easy to pass not plain object to vue extend mixin I ve add a similar issue in and it be still not fix |
vuejsvue | compute property don t receive component s instance as first argument in ssr | Bug | version 2 5 17 reproduction link step to reproduce clone install dependency run npm run ssr serve what be expect should render the app what be actually happen when you start the server you should see that application throw follow error can not read property store of undefined this happen because in ssr compute property don t receive component s instance as the first argument therefore I can not access store property I be not sure if this be a bug or not I think it be because I could not find anything about in vue or vue ssr docs I would appreciate if someone could clarify this issue thank you |
vuejsvue | both move and leave trigger for remove transition group item if transition group have display flex | Bug | version 2 5 17 reproduction link step to reproduce see fiddle what be expect only a leave be trigger when remove any item from the list display with display flex what be actually happen both a leave and a move be trigger |
vuejsvue | vue server renderer camelcase local directive be not apply in ssr | Bug | what problem do this feature solve currently ssr directive can be only pass in with kebab case key this isn t denote anywhere except in the test luckily and not intuitive as they can be provide as camelcase one on the client as well can we introduce camelcase ssr directive I d be available to work on the impl what do the propose api look like js directive classprefixer node dir |
vuejsvue | vue template remove whitespace immediately after inside of a pre | Bug | version 2 5 17 beta 0 reproduction link step to reproduce 1 run a unit test what be expect newline after input be preserve what be actually happen newline after input be remove |
vuejsvue | override a binded prop with hypenate syntax instead of camelcase not work | Bug | version 2 5 17 reproduction link step to reproduce create two child component with the same prop in camelcase bind prop from first child to second try to override camelcase prop in hypenate syntax from first child to second what be expect prop override correctly what be actually happen prop keep parent value meet this issue because I have a camelcase code stye but eslint vue recommend throw an error if prop be not hypenate |
vuejsvue | memory leak when use async component | Bug | version 2 5 17 reproduction link step to reproduce 1 load the reproducer and take a memory heap snapshot search the heap you will find 4 vuecomponent app container child async child image 2 click the destroy button this toggle a v if which will remove child component and thus asyncchild component as well 3 at this point the page be update as expect 4 take another memory heap snapshot search the heap again for vuecomponent and you will see that 4 vuecomponent still exist image image what be expect after destroy child component the component and it s asynchronously load child component should be destroy and the memory free up what be actually happen vue be hold on to a context reference which be prevent these component from be garbage collect this be happen due to the resolve async component logic locate here l57 l68 in the forcerender function on line 64 after call forceupdate the contexts array should be clear to free up those reference so that the component will be able to be garbage collect at a later point in time |
vuejsvue | immediate watcher skip parent s errorcapture and jump straight to the top error handler | Bug | version 2 5 16 reproduction link step to reproduce simply open and run the sandbox should show the error instead of get an alert that app vue catch the error in helloworld s watcher the error escape all the way to the top level to see the expect behavior open hello world and set the watcher to immediate false then hit the button to trigger the watcher in this case the error be catch by the parent app vue in the immediate case this do not happen what be expect error in immediate watcher should be catch by the parent component s s errorcapture what be actually happen the error escape to the nexttick hander this handler have no ctx or vm to pass to the errorhandler when errorhandler do not receive a vm it can not call the parent errorcapture handler this appear to be an oversight in src core instance state js in the case option immediate be true cb call vm watcher value should be wrap in a try catch that explicitly call handleerror with the vm a propose fix if option immediate try cb call vm watcher value catch e handleerror e vm immediate call for watcher watcher expression |
vuejsvue | maximum call stack size exceed in ssr with a v for with 1000 component | Bug | version 2 5 16 reproduction link step to reproduce sorry I fail to visit gist or other online code share platform just run the follow script with and instal but in node 6 it be ok process env vue env server very important const vue require vue const renderer require vue server renderer createrenderer vue component c child template const vueinstance new vue template datum item array 1000 fill 0 console log start to rendertostre renderer rendertostre vueinstance error html if error console error render error n error stack return console log what html what be expect output the html what be actually happen render error rangeerror maximum call stack size exceed at insert timer js 158 16 at object export unrefactive timer js 149 3 at writestream unreftimer net js 260 12 at writestream socket writegeneric net js 723 8 at writestream socket write net js 786 8 at dowrite stream writable js 387 12 at writeorbuffer stream writable js 373 5 at writestream writable write stream writable js 290 11 at writestream socket write net js 704 40 at write console js 108 12 someone use to mention this bug but without reproduction |
vuejsvue | functional component with multiple root don t render properly when use with v for | Bug | version 2 5 16 reproduction link step to reproduce create a functional component that return multiple root element via an array I e javascript return h span h span then use the functional component alongside v for html what be expect it should render the functional component as expect what be actually happen the render view contain undefined for each item in the array the jsfiddle demonstrate how wrap the functional component in a |
vuejsvue | v model lazy be not update the value of an input when it have a focus | Bug | version 2 5 16 reproduction link step to reproduce 1 type jacob into the input 2 hit enter what be expect value property of the input element should be change to joseph as be the value of the name property in the vue instance what be actually happen value property of the input element be not be change the value of the input be correctly be update when use v model without lazy modifier |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.