repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
vuejsvue | component be destroy and then mount | Bug | version 2 5 16 reproduction link step to reproduce run the provide jsfiddle what be expect the component in the slot should be move from the table to the div element or a new one be create and the old one be destorye what be actually happen if a slot be move from a table to a div use a v if directive the slot ist recreate but before the new component be mount vuejs pick the wrong component to destroy it destoye the new component instead of the old one |
vuejsvue | v pre be still parse compile custom component | Bug | version 2 5 4 reproduction link step to reproduce as you can see the element be still render while the element be not render as in the test here what be expect what be actually happen hello world |
vuejsvue | can not read property pende of null when use transition component | Bug | version 2 5 16 reproduction link step to reproduce 1 open fiddle and type anything into the first field mark break 2 see in the console the error message error in nexttick typeerror can not read property pende of null 3 notice that vue have stop work 4 refresh the fiddle and type anything into the second field mark work 5 notice that everything work as expect what be expect when the value of the input field be foo the compute property bar will evaluate to true and the a span will display when the user change the value in the input field from foo to anything else the compute property bar will evaluate to false and the b span render use v html will display what be actually happen initially the value of the input field be foo and the compute property bar be evaluate to true so the a span be display but when the user change the value in the input field from foo to anything else vue crash and this error message be display error in nexttick typeerror can not read property pende of null it take this very specific scenario for the error to appear in the fiddle I ve show that by remove the click show show event listener vue work as expect with no error here be three other change that when make individually result in vue work as expect remove the component surround the a span use b instead of use v show bar and v show bar instead of the v if bar and v else directive find via this question on stack overflow |
vuejsvue | typescript type null be not assignable to type propvalidator | null | version 2 5 16 reproduction link ts vue component union prop prop anything null primitive string number object cat user regex regexp mixed regexp array union user number as new user number require annotation datum this anything this primitive this object this union this regex compile this mixed return fixedsize this union step to reproduce paste it into option test ts and run yarn test type what be expect no error type should be any what be actually happen type null be not assignable to type propvalidator it work with strictnullcheck disable but the type be instead of any |
vuejsvue | vue js mustach not correctly render only after indent root element | Bug | version 2 5 16 reproduction link step to reproduce this issue happen when the root element be not indent and the mustache be split into several line html only when the root element be indent the mustache get render correctly html what also work be when mustache be put into a single line and the root element be not indent html what be expect the mustache should bind datum what be actually happen the mustache get render plain text only want to prettify my code so I split the mustache into several line and remove the indent of the root element |
vuejsvue | functional component fail depend on the sibling around it | Bug | version 2 5 16 reproduction link step to reproduce 1 create a functional component that return several root nodes 2 use it with be bind like with no sibling around it 3 render the template what be expect render correctly what be actually happen render a string undefine with no console error it be interesting that it may render successfully depend on the sibling around it there be several example in the link |
vuejsvue | component call update hook after it be destroy | Bug | version 2 5 2 reproduction link step to reproduce 1 click the home link 2 click the test link what be expect after the home component destroy its update hook should not be call what be actually happen after the home component destroy its update hook be call here be the log information home beforecreate home create home beforemount home mount test beforecreate test create test beforemount home beforedestroy home destroy test mount home update why the home component can call update hook after it be destroy be vue design to do so |
vuejsvue | bind event with once get reuse in v if else condition | Bug | version 2 5 16 reproduction link step to reproduce enter 3 in the input field and click the link test btn 2 what be expect it should only trigger the on click event that be configure for the test btn 2 what be actually happen it trigger the function bind to test btn 1 and then trigger the test btn 2 this only happen when I use v if in the parent element of the link but if I use v show it doesn t have the issue |
vuejsvue | compilation of mustache in mustache expression doesn t work | Bug | version 2 5 17 beta 0 reproduction link step to reproduce 1 use in the datum bind html true what be expect what be actually happen |
vuejsvue | prop of component in conditionally render slot stop be reactive | Bug | version 2 5 14 reproduction link step to reproduce click update message button add dot after message once alter button be click the message be no long update what be expect update message continue work even after slot be alter what be actually happen prop value stop be reactive without error nor warn this behavior take place after v2 5 14 include v2 5 17 beta 0 any version 2 5 13 and low work as expect unit test can be find in my github I be understand this be edge case and refactoring structure to avoid place identical slot in conditional position resolve my problem however this behavior be not occur in old version and suddenly change without error or warning so I be consider this be a bug and report to let you know |
vuejsvue | prop change do not always trigger watch in ie11 | Help Wanted | version 2 5 16 reproduction link step to reproduce open jsfiddle in ie11 and scroll the scrollbar up and down rapidly observe the console warn that occur when a prop update be miss what be expect the watch should be fire for every scroll event what be actually happen vue be handle subsequent scroll event before the watch be fire in my use case we be integrate with another system and it be important that we don t skip event this change be reproducible in version 2 4 3 you can change the version to 2 4 2 in the reproducer to see the correct behavior look at the change log it seem like this commit be a likely culprit |
vuejsvue | unexpected duplicate presence of slot | Bug | version 2 5 2 reproduction link step to reproduce 1 I create component with scope slot appswitcher vue 2 then I use it in another component with their own slot helloworld vue with slot subtext 3 add some element to slot div in app vue what be expect it should work without error what be actually happen change in appswitcher vue caus duplicate presence of slot subtext find in the same render tree error but there be no duplicate also add slot scope to div in app vue solve problem and no error there but why it happen without slot scope |
vuejsvue | scope slot not acknowledge in nest template tag | null | version 2 5 16 reproduction link step to reproduce just execute the jsfiddle you ll notice the scope slot isn t be render what be expect for the scope slot to be render what be actually happen the scope slot be not in this scopedslot and not be render the minimal reproduction be a little unpractical because who would unnecessarily nest content in an attribute less template tag this jsfiddle be more reflective of the real use case we re deal with |
vuejsvue | innerhtml make the content of element lose in ie11 | null | version 2 5 16 reproduction link step to reproduce 1 click click button it would execute otherbox innerhtml to clear all the content of other box 2 watch the app el be all right or not what be expect app el s content be correct in all browser what be actually happen chrome app el s content be correct firefox app el s content be correct ie11 app el s content be empty this bug would appear in ie11 but not in chrome firefox |
vuejsvue | inconsistent behavior between functional component and normal one | null | version 2 5 16 reproduction link step to reproduce 1 create a component with a slot and add some fallback content to the slot 2 create a component with render function h h and use it as the slot content 3 create a functional component with render function h h and use it as the slot content what be expect fallback content should be render what be actually happen for the normal component fallback content be clear and a comment node be render for the functional component the fallback content be render relate issuecomment 373131958 |
vuejsvue | name slot win t render | Bug | version 2 5 15 reproduction link step to reproduce the jsfiddle link reproduce the issue but it s a pretty intricate combination that reproduce it remove the slot namedslot from the div and wrap it with |
vuejsvue | transition class leave to not remove if hide element change too fast with v show | Bug | version 2 5 13 reproduction link step to reproduce change a value in a vue really fast and the transition win t remove the leave to class what be expect the label should be show what be actually happen the label isn t show on my own app I redirect to a page that be suppose to have no app header but it then redirect to another page that do but the header be miss anyway |
vuejsvue | when add and remove style rule like background sub rule background color be not re apply | Bug | version 2 5 13 reproduction link step to reproduce add background set value to red click add see the box in red click on remove check the box what be expect the box should be gray again what be actually happen the box have no background color this bug be find by matwaligora in discord the problem be that when we update style we do not reapply background color and other property because they be already apply but in the browser if you apply background it will modify the other style backgroundcolor style backgroundposition etc so we think style do not need to be reapplie but because set background have some side effect we need to reapply all other background property it s probably the same with other rule like border |
vuejsvue | assign ref to zero result in miss element in ref | Bug | version 2 5 13 reproduction link step to reproduce assign any element with ref to 0 such as what be expect p exist in ref what be actually happen p isn t in ref workaround be to put additional char to ref such as now that p will be in this ref reference |
vuejsvue | listener be not update correctly on component reuse | Bug | version 2 5 13 reproduction link step to reproduce 1 click emit1 alert something no problem 2 click switch 3 click emit2 alert again not expect what be expect not alert when I click the button emit2 what be actually happen alert when I click the button emit2 not consider the edge case listener be remove on component reuse perhaps a bug at line 260 in v2 5 13 src core instance lifecycle js |
vuejsvue | pitfall of vue dependency detection may cause redundant dependency | Bug | version 2 4 2 reproduction link step to reproduce click the button then app component will update twice what be expect app component update only once what be actually happen app component update twice when prop use in child component initialization they will be detect as dependency of parent component be there possible to stop dependency detection when enter child component initialization |
vuejsvue | keep alive doesn t call destroy if view be active | Bug | version 2 5 13 reproduction link step to reproduce 1 navigate to page a to make keep alive to cache page a component 2 navigate to page b to make keep alive to cache page b component 3 now if remove cache of page a page a be destroy correctly if navigate back to page a and remove cache of page b page b be not destroy what be expect page b be destroy what be actually happen page b be be not destroy l44 |
vuejsvue | filter with empty argument cause error in chrome 57 | Bug | version 2 5 13 reproduction link step to reproduce in chrome 57 and 56 1 filter with empty argument html text somefilter 2 when no parenthesis html text somefilter what be expect 1 no error 2 no error what be actually happen 1 in chrome 57 and 56 report error vue warn error compile template text somefilter invalid expression unexpected token in s f somefilter text raw expression text somefilter find in 2 no error I have also examine the chrome 58 and 63 which have no error both so I guess this bug only occur in chrome 57 mac chrome57 win chrome57 |
vuejsvue | layout calculation in beforeenter hook will cancel enter animation for transition element | Bug | version 2 5 13 reproduction link step to reproduce 1 click toggle slide to enable transition which be currently not work 2 if you remove the scrolltop layout calculation in beforeslideenter the element will slide in smoothly now the transition be work what be expect gradual slide in from right what be actually happen with scrolltop calculation the enter transition be go I have find that wrap the child component in an additional div will solve this problem however this seem like a hack I apologize if this be not a bug I have raise this question in forum discord and stackoverflow but no one be able to answer so I have start to think that it might be a bug stackoverflow link |
vuejsvue | can t import vue use typescript and node | null | version 2 5 13 reproduction link step to reproduce clone this repo git clone install dependency npm install compile ts tsc launch app you ll see an error vue 1 default be not a constructor node build main js what be expect I can create a new vue instance use the constructor what be actually happen I get an error typeerror vue 1 default be not a constructor I believe this be relate to the issue which I ve include my comment below I m use commonj output from typescript no webpack one similarity between op and I be that we re both use the typescript baseurl option something be definitely wrong with the standard import in typescript I too be use vue 2 5 13 I m set up ssr on node 8 9 3 and typescript 2 6 my tsconfig json look like this compileroption outdir build target es6 module commonj moduleresolution node sourcemap true emitdecoratormetadata true experimentaldecorator true rootdir src baseurl src nounusedlocal true exclude node module typing I try a number of other workaround include try to load the vue esm js file via the compileroption path property without success I be get the exact same vue 1 default be not a constructor error as op |
vuejsvue | cancel transition on v show still add the entertoclass or leavetoclass | Bug | version 2 5 13 reproduction link step to reproduce cancel a transition in the next frame example cancel a fade out transition js this show false this nexttick this show true what be expect the v enter to or v leave to class be not add to the element what be actually happen the v enter to or v leave to class be still add to the element despite the transition be cancel those line should likely be put be a cb cancel guard l152 l260 |
vuejsvue | svg foreignobject svg | Bug | version 2 5 13 reproduction link step to reproduce v1 0 28 be ok v2 5 13 have bug what be expect foreignobject svg svg rect what be actually happen foreignobject svg svg rect svg foreignobject svg svg rect text |
vuejsvue | custom event emit by the v if component yet trigger the v else component listener | Bug | version 2 5 13 reproduction link step to reproduce define a custom component witch emit custom event use v if v else create 2 component instance on first instance use v on listen the custom event the second donot toggle the v if condition emit the custom event on the second instance what be expect the listener on the first instance not be trigger what be actually happen the listener on the first instance be trigger |
vuejsvue | vue do not accept undefined value when return an array in functional component | Bug | version 2 5 11 reproduction link step to reproduce check console log what be expect should render input element what be actually happen when functional component return an array and the array contain other value besides vnode like e g null or undefined vue will not render anything and throw an error I check this in few previous version and it seem that it never work correctly in 2 5 9 I get a different warning can not set property isrootinsert of null so the question be be this a case that should be handle by vue internally or do I have to be careful and not to return null undefined value in return array |
vuejsvue | vue template compiler double escape newline in ssrnode text string template | Bug | version 2 5 9 reproduction link I use a gist because ssrcompile be not expose by the global build of vue step to reproduce javascript compiler require vue template compiler template nfoo nbar n result compiler ssrcompile template console log result render output with this return c div attrs i d foo nbar ssrnode foo nbar what be expect vue template compiler should not double escape newline in attribute for ssrnode string template what be actually happen vue template compiler double escape newline in attribute of ssrnode if you look at the output from the reproduction step you will see that the newline character n be only double escape if it be part of an attribute in an ssrnode if be nor optimize to a string template and store in the attrs property be it fine and other newline that be outside attribute be also fine the bug be observe with vue template compiler v2 5 9 and node js v8 9 1 while the above example seem silly newline in attribute be very common when use responsive image with multiple size in the srcset attribute which be usually break onto one line per size url for readability and this be how a colleague of mine run into this bug where responsive image be work differently between ssr and rehydration due to the problem because the browser abort srcset parse when find the n literal string |
vuejsvue | datum method not call with this as argument when use mixin with datum option | Bug | version 2 5 9 reproduction link step to reproduce 1 run the reproduction 2 vuecomponent log in console 3 uncomment mixin mixin 4 run the reproduction again what be expect vuecomponent log in console what be actually happen undefine log in console |
vuejsvue | keep alive with include property result prop datum do not pass down to component | Bug | version 2 5 8 reproduction link step to reproduce 1 click first and second alernatively for multi times 2 change select to japanese click first and second alernatively for multi times 3 change select to english what be expect expect router view can render to first 2 or second 2 but it remain first 3 or second 3 what be actually happen keep alive be remain the initail include bind datum s value what I want be keep alive can be dynamic change to the include property s bind datum and prop datum can tranfer to component properly |
vuejsvue | ssr mismatch style be not update in the dom unless the element have a ref | Bug | version 2 5 3 reproduction link step to reproduce load the codepen this be obviously not an actual ssr app but be emulate one the same thing happen with actual ssr that set the padding base on window width what be expect the inline style should be update when the page hydrate see the codepen below what be actually happen the style only update if the element have a ref see |
vuejsvue | conditionally change the order of slot work incorrectly in env production mode of vue | Bug | version 2 5 2 reproduction link step to reproduce after open the codepen please click on the toggle button what be expect the slot which show the number should inverse when click on the toggle button their order be change with a v if condition what be actually happen the slot do not switch order the first slot seem to switch the second slot seem to stay in place instead of 1 2 to 2 1 this happen 1 2 to 2 2 we have try this with more slot and the result be unpredictable we be change the order of slot for feature that change location on small or big screen sometimes the structure of a page change too much so we change the order of slot to manage this we only notice the bug when we set the env to production all work fine in development mode |
vuejsvue | pass component to grandchildren s nest name slot will resolve in the default slot | Bug | version 2 5 2 reproduction link step to reproduce my use case be that I have a default layout with toolbar and main content wrapper but some page need a searchbar and some don t and layout may have different level so I create a component call layoutdefault as a base for other layout to use and because I want to be able to replace the default toolbar when need I put the default toolbar in with toolbar as fallback content code snippet html layoutdefault vue I make these kind of component because I want to be able to 1 replace the default toolbar if need 2 use the default toolbar but pass thing to its slot toolbarslot in above example and then in other layout component I do this html layoutlv1 vue default content from layout as you can see to pass component to grandchild s slot I use this pattern for some reason component pass use this pattern will be pass to the default slot if there s one see example 2 3 and 4 in the reproduction what be expect I expect when no nothing be pass to a name slot the fallback content will be render with it s slot too what be actually happen in example 2 the replace toolbar be render in layoutdefault s default slot in example 3 and 4 searchbar be pass to slot toolbarslot but not render be this the expect behavior or if there s a way for I to make these kind of reusable layout with each default part replaceable and if use the default part be able to pass component into their default part slot |
vuejsvue | v model with select and text area issue vue server render | Bug | version 2 5 2 reproduction link step to reproduce in ssr the select field be not render with the select attribute then the select option appear select after all page load the same happen with the textarea field first appear empty and then when the page load it show the content of v model what be expect textarea and select must render the value in ssr what be actually happen both field not render the value in ssr check this issue |
vuejsvue | conflict between v once and ref | Bug | version 2 5 2 reproduction link step to reproduce open console ctrl shift I in chrome for example what be expect output in console what be actually happen output in console undefine if remove v once or change vue version to 2 4 4 in 2 5 1 and 2 5 0 bug remain problem disappear thank |
vuejsvue | vm off not work when pass an array as first argument | Bug | version 2 5 2 reproduction link step to reproduce 1 add multiple custom event listener js this on event1 event2 console log this be callback 2 try to remove they with vm off this off event1 event2 3 try to emit the remove event this emit event1 what be expect nothing should happen because the event listener should have be remove what be actually happen get this be callback print in the console which mean that the event listener be not remove as expect please check my post in vue forum for more detail |
vuejsvue | keep alive include will also cache anonymous component | Bug | version 2 5 2 reproduction link step to reproduce triggle the route what be expect the second route component not be cache what be actually happen the second route component be cache this demo tow router view component both have name the result be right but in this demo the second route have no name but also be cache the match be first check on the component s own name option then its local registration name the key in the parent s component option if the name option be not available anonymous component can not be match against when l keep alive router view every anonymous component page will be cache I don t think be reasonable |
vuejsvue | v if v else not work with type v model | Bug | version 2 5 2 reproduction link step to reproduce run the jsfiddle example what be expect v else to work what be actually happen v else seem to have no effect maybe relate duplicate with issue 6917 or issue 6907 |
vuejsvue | grandchild component disappear after parent re render | Bug | version 2 5 2 reproduction link step to reproduce on the jsfiddle wait for the settimeout on l19 to finish when the parent s label be set to false the component re render but lose the content of the grandchild what be expect for the grandchild content to still be in the dom what be actually happen grandchild disappear after component in the parent re render be expect this bug to be fix with this issue not sure if it s the same or just a similar issue |
vuejsvue | compute property setter on component other than this not call when update v model | Bug | version 2 5 2 reproduction link step to reproduce 1 declare a compute property on a parent component with a setter 2 in a child component pass the compute property as a v model 3 attempt to update the property via the v model bind what be expect the compute property setter be call what be actually happen the compute property setter be not call and the follow message appear in the javascript console vue warn avoid add reactive property to a vue instance or its root datum at runtime declare it upfront in the data option this appear to be a regression in vue 2 5 0 as change the vue version in the provide jsfiddle to 2 4 0 fix the bug the optimisation apply early in the 2 x series to declare compute property on the component s prototype appear to interfere with the call to hasown in function set in observer index |
vuejsvue | ssr issue with dynamic type | Bug | version 2 5 2 reproduction link unable to quickly setup a ssr environment to show the issue step to reproduce vue what be expect generate html by the server what be actually happen the server generate hydration error in browser console vue warn the client side render virtual dom tree be not match server render content this be likely cause by incorrect html markup for example nesting block level element inside or miss bailing hydration and perform full client side render uncaught in promise typeerror can not read property tolowercase of undefined at emptynodeat vendor js 18438 at vuecomponent patch as patch vendor js 19011 at vuecomponent vue update vendor js 15663 at vuecomponent updatecomponent vendor js 15791 at watcher get vendor js 16134 at new watcher vendor js 16123 at mountcomponent vendor js 15795 at vuecomponent webpackjsonp node modules vue dist vue runtime esm js vue 3 mount vendor js 20834 at init vendor js 17087 at hydrate vendor js 18887 |
vuejsvue | doesn t select correct option after render | Bug | version 2 5 2 reproduction link step to reproduce in the link nothing in your own instance set a v if on a select that also have a v model see example what be expect the select should render and the option whose value be the value of the model bind to the select should be select what be actually happen the first option in the select be active until either a call to forceupdate or another model be change click into the text field and type a letter then suddenly the correct value be select in the dropdown this use to work in vue 1 I upgrade and then discover this I m work around it for now with a this nexttick this forceupdate I previous submit this issue as 6882 however I believe gebilaoxiong close it prematurely the provide solution change the functionality and do not solve the actual issue |
vuejsvue | inconsistent state possible after middle click on refresh icon on firefox 56 | null | version 2 5 2 reproduction link step to reproduce 1 be on firefox 56 or more 2 check the checkbox 3 middle click on the refresh icon in the toolbar what be expect a consistent state either unchecked and false or check and true what be actually happen the state be check and false on chrome the result state be unchecked and false on firefox 55 or less the result state be check and true happen on radio with all input except the textarea and text one the number input result in a consistent state too I couldn t make a jsfiddle for it because firefox doesn t attempt to restore input state after a midlle click refresh on jsfiddle |
vuejsvue | dynamic input type only work if the property be call type | Bug | version 2 5 0 reproduction link step to reproduce if you use a dynamic type on an input and the property be not call type you ll get this warning vue js 491 vue warn property or method type be not define on the instance but reference during render make sure that this property be reactive either in the data option or for class base component by initialize the property see declare reactive property find in and it win t work if you switch from a normal type like text to a checkbox or radio button the special type that be in the else branch diff 6eaa1698ef4f51c9112e2e5dd84fcde8r4 click the button click I to switch the input to a checkbox then try check and unchecke the box the model s value will not change call the property type work the model s value will change what be expect dynamic input type should work regardless of the property name what be actually happen dynamic input type only work if the property be call type |
vuejsvue | memory leak with keep alive | Bug | version 2 4 4 reproduction link step to reproduce switch foo and home link for several time vuecomponent s count will be always grow up what be expect vuecomponent s count be stable what be actually happen vuecomponent s count always grow up 1 switch 0 time 1 2 switch 20 time 2 3 switch 100 time 3 when the component be big chrome s memory will be not enough thank you for your reading |
vuejsvue | uncaught typeerror can not read property type of undefined | Good First Issue | version 2 4 4 reproduction link step to reproduce bind a component to in input field while use inline template what be expect a proper error message that tell the developer that inline template component must have exactly one child element what be actually happen uncaught typeerror can not read property type of undefined hello there be already a proper error message for this situation it s just that the check for the number of child element be implement as 1 maybe it should be 1 the method geninlinetemplate which throw the exception can be find here l2994 |
vuejsvue | transitioning between component fail when component s root node have v if false | Bug | version 2 4 4 reproduction link step to reproduce click radio b what be expect should switch to component b what be actually happen doesn t switch to b in real scenario when a user navigate to a new view I want to load the remote datum in create hook and set the root node s v if to true to switch the component in but when data hasn t be load for some reason the dynamic component be stuck and can t go anywhere |
vuejsvue | embed html into an html5 svg fragment get wrong namespace in template | Bug | version 2 4 4 reproduction link step to reproduce embed in the svg element what be expect the should be render as a htmlelment and show what be actually happen do not show seem related to this |
vuejsvue | vue ssr bug on nodejs v8 x about async promise entrance | null | version 2 4 4 reproduction link step to reproduce babel webpack dev server object promise what be expect babel async async what be actually happen normalizerender undefined sorry my english be poor babel webpack dev server object promise ssr vm promise async promise babel async promise co object function async promise object function object promise node modules vue server renderer build js 7791 javascript var re evaluate entry createsandbox usercontext resolve typeof re function re usercontext re re promise javascript var re evaluate entry createsandbox usercontext if object prototype tostre call re object promise re then fn resolve typeof fn function fn usercontext fn else resolve typeof re function re usercontext re promise resolve |
vuejsvue | null value for v text directive not handle in ssr | Bug | version 2 4 2 reproduction link v text v text step to reproduce try to render where x be be null or undefined what be expect it may be gracefully handle just like v html directive see note below or client side version of v text what be actually happen throw an internal typeerror bash can not read property replace of undefined js function escape s return s replace g escapechar seem the simple fix would be define a default value for s parameter in util js l46 or well do a string type check on value relate to nuxt nuxt js 1638 some note v html behaviour also differ in ssr and client ssr render v html null while it change into on client side seem be be optimize into vm foo so we can change it into vm foo to handle this inconsistency during ssr render |
vuejsvue | click would trigger event other vnode click event | Bug | version 2 4 2 reproduction link step to reproduce see reproduction link what be expect when I click expand be true then expand to become false and only counta change what be actually happen when I click expand be ture nothing happen the counta and countb change I guess when I click expand change to false but immediate the click event trigger it execute another vnode click event then expand change to true and more if I rename the second div to another tag name such as p section no error occur if I move click event from I tag to parent div tag in the first div no error occur |
vuejsvue | input once prevent the update of the input if use with v model | Bug | version 2 4 2 reproduction link step to reproduce type one character in the input what be expect the character be add to the input the value property be update to reflect the change and the setdirty method be call set isdirty to true what be actually happen the setdirty method be call but nothing be add to the input and the value do not update after the first character entry into the input the model bind work as expect it seem that use input once somemethod be prevent the expect behavior of v model find via this stackoverflow question |
vuejsvue | vue ssr fail with innerhtml | Bug | version 2 4 2 reproduction link step to reproduce use dompropsinnerhtml in jsx or v html in vue template or clone the repo npm install npm run dev open and what be expect no warning in console what be actually happen dom mismatch error v html work fine when there be no child but fail if there be one option be to completely ignore innerhtml and v html in vue ssr basically comment this line l27 solve the problem another option be evaluate innerhtml before compare dom snapshot so you get value from innerhtml on static ssr render website without dom mismatch third option be ignore child in createelment if there be innerhtml domprop I think this one be the good |
vuejsvue | ie11 keystroke miss if v model be use | Bug | version 2 4 2 reproduction link step to reproduce this issue only occur in internet exporer 11 on textarea and input field when use v model bind 1 open the with ie 11 2 quickly enter text into the second textarea maybe you should press 3 button at same time we use a barcode scanner to enter the text but its also possible to reproduce it with the keyboard we also recognize that it happen more often on slow machine what be expect all key be recognize what be actually happen some letter be miss randomly we make a video of this behaviour you could reproduce this even on the vuejs page text I just add a v on input to the textarea to see what s log there the result be a a ac ac the b be never recognize even in input event I also change the intercharacter delay of the scanner from 1 ms to 25 ms without success |
vuejsvue | vm forceupdate duplicate content when child consist of a slot follow by text | Bug | version 2 4 2 reproduction link step to reproduce in a component render function return an element that contain a slot directly follow by raw text what be expect new content completely replace the old content on re render what be actually happen new content be append to the old content on re render seem like this be fix for render function compile from template in 2 1 5 release note for that version say small across the board performance improvement for render function compile from template they now skip the normalization of nest child array base on information infer from the template at compile time I couldn t reproduce this in vue file in a project generate from vue cli webpack template jsx be affect as can be see in this issue and render function as see in the link fiddle |
vuejsvue | inject provide not work in vue extend class | Bug | version 2 4 2 reproduction link step to reproduce 1 use vue extend to create a subclass which contain provide option 2 inject property in child component of subclass what be expect property be inject correctly what be actually happen property be not inject in src core util option js line 97 99 defaultdata be set to undefined if parentval be not a function it may cause this issue |
vuejsvue | component disappear on first re render | Bug | version 2 4 2 reproduction link step to reproduce on the jsfiddle wait for the settimeout on l15 to complete after two second what be expect for customela to still be in the dom what be actually happen customela be remove from the dom on re render however it come back on the third re render test use setinterval instead of settimeout on jsfiddle on l16 the jsfiddle be use vue v2 4 0 but I have verify the bug on v2 4 2 locally |
vuejsvue | vue server renderer lt hello will cause server client dom mismatch | Bug | version 2 4 2 reproduction link step to reproduce just make an ssr app use nuxt or something else and put hello into the template what be expect no error what be actually happen console output vue warn the client side render virtual dom tree be not match server render content this be likely cause by incorrect html markup for example nesting block level element inside or miss bailing hydration and perform full client side render |
vuejsvue | attrs be undefined when component have no prop | Bug | version 2 4 2 reproduction link step to reproduce access attrs as object within component context when no prop be provide what be expect attrs be an object contain unrecognized prop therefore I would expect an empty object when no prop be specify on component tag what be actually happen attrs be undefined |
vuejsvue | out in transition issue with async component in a block | Bug | version 2 4 2 reproduction link step to reproduce open click the b button what be expect the previous component a should disappear before component b appear what be actually happen component a and b be visible simultaneously see also issue 5760 |
vuejsvue | dt and dd without end tag go to wrong | Bug | version 2 4 2 reproduction link step to reproduce 1 write and without their end tag by turn in a template except dom template for example html title 1 detail 1 title 2 detail 2 what be expect the dom tree will become html title 1 detail 1 title 2 detail 2 what be actually happen the dom tree become html title 1 detail 1 title 2 detail 2 |
vuejsvue | select element can t be render correctly by vue 2 0 0 or above in ie 11 | Bug | version 2 4 2 reproduction link step to reproduce 1 open the link in ie11 2 see the select element do t be render correctly what be expect the second option in select element should be in view what be actually happen the third option in select element be still in view I have to use settimeout to solve this problem so I want to know how it happen |
vuejsvue | error compile template even though one root element | Bug | version 2 4 1 reproduction link step to reproduce 1 tag as root element 2 put tag as child element what be expect render template correctly what be actually happen error compile template with message component template should contain exactly one root element |
vuejsvue | html block comment single quote not parse correctly | Bug | version 2 4 1 reproduction link step to reproduce use the new comment true property on a vue instance do not understand block comment and it also error when single quote be use within inline comment this be particularly annoying in drupal development when debug template since the template debug output be do use block comment and contain single quote see codepen example for a typical drupal comment block output what be expect comment should be render correctly within the output html what be actually happen vuejs fail to render the instance and throw an exception when try to parse the comment I believe this would happen when use drupal 7 or 8 with development debugging turn on when use vue 2 4 |
vuejsvue | custom directive insert hook doesn t fire when transition be use on bind element | Bug | version 2 3 4 reproduction link step to reproduce 1 create custom directive that use insert hook 2 apply that directive to element with v if and wrap in 3 toggle visibility of that element what be expect insert hook to fire just like bind hook what be actually happen insert hook doesn t fire at all I ve spend like couple of hour debug this on my custom directive vuebar because I think this be issue with my code unfortunately I think that s issue with vue itself there be a workaround though just wrap element with directive in another element that will get transition like in 3rd example in the reproduction |
vuejsvue | strange behavior with input type number | Bug | version 2 3 4 reproduction link step to reproduce I want to build a input with 6 digital the code above woks fine until I enter 0 more then 6 time val in vue model be 000000 but the display be 00000000 what be expect I think it s a bug what be actually happen I don t know |
vuejsvue | v model not work with | Bug | version 2 3 4 reproduction link step to reproduce see minimal reproduction link v model work as expect with but not with the longhand work when the model prop be name something other than value what be expect v model should automatically wire up the value prop with its expression what be actually happen no value be be pass to the value prop I m get the default value undefined instead my only guess be that v model be bind before the component be mount |
vuejsvue | transition group with dynamic name not correctly apply transition | Bug | version 2 3 0 reproduction link step to reproduce 1 run the fiddle 2 uncheck the checkbox 3 click shuffle button 4 check the checkbox 5 click shuffle button what be expect after first shuffle click with an unchecked checkbox list item be reorder with no transition animation after second shuffle click with a check checkbox list item be reorder with a transition animation what be actually happen after first shuffle click with an unchecked checkbox list item be reorder with no transition animation after second shuffle click with a check checkbox list item be still reorder with no transition animation find via this question on stackoverflow 44851948 if the list be shuffle before initially unchecke the checkbox everything work as expect I m only see this when the list be initially shuffle when the name of the transition group be set to disabled list |
vuejsvue | ssr unexpected hydration bailout with tag | Bug | version 2 3 4 reproduction here what happen on f5 reload key ssr pre tag issue it happen only once the video be loop step to reproduce add a tag in app vue of the vue hackernew 2 0 demo |
vuejsvue | memory leak in vue js server side when use compute | Bug | version reproduction link step to reproduce 1 use vue server render rendertostre 2 the vm in server have compute which define a test function without return yes this step be incorrect just throw error and pause be ok but then memory leak happend 3 memory leak happend what be expect throw error and pause what be actually happen the vonde be go to run and create but not destroy and exit in heap snapshot I find the vue 2 have create almost 4538 just look in |
vuejsvue | can not read property ssrcontext of undefined | Bug | version 2 3 4 reproduction link l13 l13 step to reproduce 1 git clone 2 change src util title js file like this js const servertitlemixin create before change const title gettitle this if title this ssrcontext title vue hn 2 0 title after change const title gettitle this vue hn 2 0 if this ssrcontext this ssrcontext title title accord to functional and robustness the change code should be ok as normal thinking 3 npm install npm run dev 4 open browser enter what be expect the if condition statement ensure this ssrcontext to be not undefined when try to set title a value on it it shoud be ok as normal expect what be actually happen error trace in console text vue warn error in create hook typeerror can not read property ssrcontext of undefined find in error during render typeerror can not read property ssrcontext of undefined at vue 3 get d temp vue demos vue hackernew 2 0 node module vue dist vue runtime common js 4423 23 at vue 3 create src util title js 20 21 at callhook d temp vue demos vue hackernew 2 0 node module vue dist vue runtime common js 2554 21 at vue 3 vue init d temp vue demos vue hackernew 2 0 node module vue dist vue runtime common js 3998 5 at new vue 3 d temp vue demos vue hackernew 2 0 node module vue dist vue runtime common js 4093 8 at new store d temp vue demos vue hackernew 2 0 node modules vuex dist vuex js 264 21 at createstore src store index js 10 9 at createapp src app js 21 16 at module export webpack export default src entry server js 13 35 at module export webpack export default src entry server js 11 9 error in browser 500 internal server error I suppose it be a bug of vue server renderer if not what happen |
vuejsvue | inconsistent behavior of v model sync during ime composition for | Bug | what problem do this feature solve basic usage for language that require an ime chinese japanese korean etc you ll notice that v model doesn t get update during ime composition msg be ok but type search be not ok msg what do the propose api look like for language that require an ime chinese japanese korean etc v model type search doesn t get update during ime composition |
vuejsvue | keep alive component or other abstract component ignore slot name | Bug | version 2 3 4 reproduction link step to reproduce just open reproduction link what be expect foo content be show at foo slot default slot foo slot foo content what be actually happen foo content be show at default slot slot foo specification be just ignore default slot foo content foo slot slot name be store in datum and lose at this line l171 be this an intentional behaviour |
vuejsvue | out in transition issue with async component | Bug | version 2 3 0 reproduction link step to reproduce load click the b button what be expect the previous component a should disappear before component b appear what be actually happen component a and b be visible simultaneously this behavior be happen only when component b be not already load next time you switch from a to b everything be fine |
vuejsvue | even after async component be resolve a timeout occur | Bug | version 2 3 2 reproduction link step to reproduce after reproduction link be load wait what be expect when async component be resolve a timeout be not occur what be actually happen when async component be resolve a timeout be occur the follow error in console log vue js 437 vue warn fail to resolve async component component new promise resolve settimeout resolve template load 200 loading template loading error template timeout delay 200 timeout 3000 reason timeout 3000ms |
vuejsvue | element unnecessarily re create when an above v for change | Bug | version 2 3 2 reproduction link step to reproduce change the input mark change I then add a row any input follow the v for row get re create and lose their value while input above remain as they be this only seem to happen when the input and v for element be contain in a parent component s slot what be expect all input remain unchanged regardless of what happen to the sibling v for element what be actually happen any input element follow the v for be re create reset their value |
vuejsvue | dynamic slot name bind from v for directive not work with scope slot | Bug | version 2 3 2 reproduction link step to reproduce create a scope slot use the |
vuejsvue | keep alive inside of transition not work with include | Bug | version 2 2 6 reproduction link step to reproduce click the switch view button what be expect the home view s state should have be keep alive when switch to the other signin view what be actually happen instead the home view be recreate everytime if I remove the include home option from keep alive it work as intend or if I remove the mode out in option from the transition node it also work as intend I ve debug this and it seem that when every time it switch the component the include watch be somehow trigger with undefined as val parameter and then it s be trigger again with the correct home value but by then the first trigger have already remove the home node from the cache |
vuejsvue | mouse modifier click right not work | Bug | version 2 2 1 reproduction link step to reproduce click on the textarea with the right click of your mouse what be expect it should add in the textarea the follow text contextmenu right what be actually happen there be only the text contextmenu |
vuejsvue | view not update when use transition in this case | Bug | version 2 2 6 reproduction link step to reproduce click the update text what be expect position change what be actually happen position not change it work when I do like this |
vuejsvue | input type file be change to text in safari | Bug | version 2 2 4 reproduction link step to reproduce html file js js const app1 new vue el app datum enterus true user sean settimeout app1 enterus false 1000 wait one second for the timeout to expire and the view to change what be expect the second view consist of the head file and a file input should appear what be actually happen a text input appear instead inspect the dom also show a input element with type text be create this bug seem to occur only in safari 10 0 3 |
vuejsvue | v show doesn t not work for component on server side rendering | Bug | version 2 2 4 reproduction link step to reproduce npm install node server js what be expect html hello world what be actually happen html hello world |
vuejsvue | provide isn t reactive with a single array | Bug | version 2 2 4 reproduction link step to reproduce create a parent and child component set the provide of the parent use vuex inject the provide of the parent to child what be expect must be reactive what be actually happen not reactive |
vuejsvue | can not register vuex in create hook with performance on | Bug | vue js version 2 2 4 reproduction link on line 20 change the vue config performance from true to false to switch between normal behavior and the issue behavior step to reproduce attempt to register a vuex module in a beforecreate or create hook with the performance option set to true will prevent vue from render what be expect if the fiddle execute correctly the follow text should be display hello from default module hello from register module what be actually happen uncaught domexception fail to execute measure on performance the mark vue perf init do not exist typeerror can not read property option of undefined other some quick messing about I ve find that this bug be introduce sometime after 2 2 1 |
vuejsvue | bind an array to an input field | null | vue js version 2 2 4 step to reproduce arraydata function return 1 2 3 what be expect early version of vue 2 1 9 would set the value of the input field to 1 2 3 but now the value be set to 1 2 3 which be the valid representation of an array json decoding do not work with the latter format |
vuejsvue | no change trigger after reassign state | Bug | vue js version 2 2 4 reproduction link what be expect state declare in root component should change and render to html same code in vue version 2 0 0 work as expect what be actually happen state change in the callback emit by child component be not work as expect |
vuejsvue | use arrow function inside v on with key modifier doesn t wok | Bug | use an arrow function inside v on directive together with a key modifier doesn t work fiddle to test it yourself I ask in a forum thread first it be mention that this could be a bug |
vuejsvue | default value not show for default slot when only name slot content provide | Bug | vue js version 2 2 1 reproduction link step to reproduce have two slot one name and the other be default and template provide only other slot content the default slot do not show default value because empty node be register with empty space as content |
vuejsvue | inject falsy value | Bug | version 2 2 1 reproduction link step to reproduce view generate output what be expect provide falsy value should be injectable what be actually happen check in inject js l16 l16 prevent injection of falsy value |
vuejsvue | v2 2 0 beta 1 v model doesn t work when pass prop be name value | Bug | vue js version v2 2 0 beta 1 reproduction link 2 2 0 beta 1 2 1 10 step to reproduce open 2 2 0 beta 1 repo link type something in the first input field value prop in the parent component should update what be expect v model should work regardless of the name of pass prop what be actually happen when v model prop name be value v model doesn t update the datum when input event be fire it ony break when be use on custom component it work fine in 2 1 10 |
vuejsvue | unexpected behaviour when use appear mode attrib | Bug | vue js version 2 1 10 reproduction link a variant with css transition a variant with js transition step to reproduce css click run on jsfiddle js click any button in result pane what be expect css not work appear attribute do not work initial animation js not work mode out in attr after click the button disappear block in comp if you remove this attribute then the block do not disappear but the animation leave enter be trigger simultaneously what be actually happen this be my first app on vue I don t know I want to know be the problem in my code or be it a bug tnx |
vuejsvue | late inject option of constructor be drop in resolvecomponentoption function | Bug | while investigate the cause of relate to vue hot reload not work with vue class component ktsn find a bug in vue core which he note here issuecomment 280859079 he say I find there be a bug in core library that accidentally drop late inject option of constructor that mean if we use vue hot reload api or vue loader they inject some option into component option object after create component constructor then the component be instantiate by use constructor with createelement and the inject option be drop in resolvecomponentoption function l69 and that it be also cause here be the minimal reproduction of this bug by ktsn I don t know much about it I m just create the issue here for ktsn in summary this issue be cause vue class component hot reload to not work and also make use vue class component with css module impossible thank you |
vuejsvue | dynamic slot name not work with scope slot | Bug | vue js version 2 1 10 reproduction link step to reproduce 1 create a scope slot scope slot use the |
vuejsvue | issue about father component s scope style when child component show by v if | Bug | vue js version 2 1 10 the late reproduction link expect in this demo all the text be red get only 1 and 3 be red step to reproduce 1 create a father component that have a class item on each of his child vue 2 create the child vue 3 the default state of the child be hide show it like this ref child show or other what be expect expect text I m the child with red color what be actually happen black probably reason vue will add some private attribute to all the element of the component when it have scope style but forget to do it with the v if false default hide child |
vuejsvue | transition group transition on empty array | Bug | vue js version 2 1 10 reproduction link step to reproduce there seem to be an issue with the transition group component when transition be apply on each element iterate on a v for with an initial empty array whenever you add push an item to the array before the previous transition be complete all previous transition will stop but if you wait for the first transition to finish but only on the first instance and then try to add item all work as expect similar if you fill the initial array with 1 or more value all work as expect what be expect all item should continue to animate what be actually happen animation stop for all element except for the last one add it seem that vue detect a change in position and therefore replace all transition class with the move class |
vuejsvue | use in custom delimiter yield wrong compile template | Bug | vue js version 2 1 10 reproduction link step to reproduce it seem that vue parse the template string improperly if you add a space before open delimiter the rendering be correct try inside tag text what be expect correctly render what be actually happen improperly render I seem to strip the next tag in this case |
vuejsvue | server side function type prop s default function be undefined when render server side | Bug | vue js version 2 1 10 reproduction link step to reproduce 1 run the app npm run dev what be expect should render to default function result value what be actually happen throw error vue warn invalid prop type check fail for prop functionprop expect function get string find in component at user damiandulisz code private vue hackernew 2 0 src mycomp vue default function result undefine vue warn error when render component at user damiandulisz code private vue hackernew 2 0 src mycomp vue error during render top typeerror vm functionprop be not a function at proxy render vue ssr bundle 1605 48 at vuecomponent vue render user damiandulisz code private vue hackernew 2 0 node module vue dist vue runtime common js 2216 22 at rendercomponent user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 6078 25 at rendernode user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 6061 7 at next user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 6197 9 at next user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 6189 7 at object cachedwrite as write user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 36 9 at next user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 6199 17 at cachedwrite user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 36 9 at rendernode user damiandulisz code private vue hackernew 2 0 node module vue server renderer build js 6069 7 |
vuejsvue | null | Bug | vue js version 2 1 10 reproduction link what be actually happen error vm281 vue js 525 vue warn expect an array value for its binding but get string find in root instance |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.