repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
vuejscore | mutationobserver in definecustomelement be disconnect if we move the custom element to another place then lose attribute observation | Bug | vue version 3 4 21 link to minimal reproduction enp9ve1v2zam sucmcao4dnrtpoxzu2khrpdnmy71t24szkotsvbktmwgf 7kdl 6fo0l4jke0 8sg7ruthzvhvrhi3c2krjwqnfmmwhzgo09xaakzypvgijlbhondfnzs0aoxwko hgy3udmurexwtvqlvwzgpjrprppzy xk0ohqiwvhuxw3w8l2suuemduztsk7m1vel7l2wvechfnaiiuhmqdgckvrukkhmclmgxxdlchcoqwwd yygcytu2t8lgpbh dg oewrkdcgtkp0cekgqgxqa14hawjvifgm3wjp73k3obmzffkxrkdv6m4t7oc8nz7mjllsu9dwnwdqzdktylqqofengxunoxj7x8aejbxpdkjqbsn6tp 12gaayxm3tb759rvj idymcsqdzjei9 pl0nevkpnpwc9eih39m9wyue nawjfo fi3huliz4w9zwo3mjsxmjb1 mm vbxbbatknyb4roc3hfmlmujvyutygzu7hmjvxr7rhiwwkszjkgpyel k vrjdq3q2sihsq20llzmb0bp8elfnd8 t kjq8kixnvlralj0zyacgkdfhowigjpwr5sp6mjwoklotobmxxz5rebsxcv1pyzdz4pogf4wcw4ux4dgfin0naycke9olocdjbrrfno0ybumyongcdm8f5vwnsjz9b4ts32kwuu309iwszuhkfelhaoewt9ohn8wv3rca16ffb4k7jruywufb 9epry0hrey7bhlsvkthzksnhthsjucvnpcwpqq3e9f1d xme mfkwrdzj9jdxmd04rfc1py4porrsja2f gi9xo4oo7x kiirrwj 8ij 3w8ucnj1y37 iv3opwvdev6xwwoy5djf zdh8 wclhve8bbtdttwi3wj fri5bciryd9bvwhaexxle0vvvltbv 7y0qvl qjcovteel6i8l2 ekp0md3p2zf ayq6f3m0jpy step to reproduce click move button then delete the two digit in input will find 0 in input or click move then click removeattr value attr of custom element be remove but inner input be not update what be expect mutationobserver in custom element should work after we move the element then the prop can be update normally what be actually happen mutationobserver be disconnect if we move the dom for the first situation we delete the two digit the num will be null but patchdomprop rumtime dom will make it 0 and remove the value attribute if mutationobserver be still on inner value will be null as the attribute be remove but it s off so we get 0 system info no response any additional comment I be do some work with documentpictureinpicture which can open a new small top level window to display any element so I have to move the element from original document to the new document then the issue occur I think we can put the clear logic of mutationobserver in next tick of disconnectedcallback of apicustomelement vue runtime dom then it will work diff disconnectedcallback this connect false if this ob this ob disconnect this ob null nexttick if this connect if this ob this ob disconnect this ob null render null this shadowroot this instance null |
vuejscore | scope style escape case | Bug | vue version 3 4 19 link to minimal reproduction enqdusfkazeq zuqhikuxaperkug0omevnrjqnbdau3njihjrpxsf3cm6a6k1yo3zhtvhjfzsubn1mzdc3zkc185aqpzefp7jrrsrhgbxzrg7k3y3jmgjbkcsmoynqgtdjgnjprjeacxqgyafwnflttwqdl7u8er7bi84shsr zjl6mqx0u tpmxd74yei4x2dibjebwje1zpaj3a4m02gs zzehrltkvf1hllgwxj1evud1ugnf hvhgt858oa6ehzgqukwebi9e7ibfb4hsjf1q1d9b3kp3qiwpcbzratrtp1ff91exrnlvxj0s1ua7fulycgpn1evob6cjvbb6p92d7oj2cf0bq yh uj3x ljle32uzimvf90me3m8g43yd3bqzztfajkthmzl0yyrgpc1djz0llpbn jx5wlsqexdms h9phti6fm6gk2ety775aihg7bc step to reproduce 1 create a new component which root node have a class name and a child 2 create a css rule for that class and create a class rule for its descendant 3 use that component in a component with an ancestor who have the same class name with that component s root node 4 the style of the node be effect by the rule which mean to take effect on its descendant because the existence of a class name out of the scope what be expect class name datum v hash class name datum v hash what be actually happen class name datum v hash class name datum v hash system info no response any additional comment no response |
vuejscore | v bind shorthand 3 4 do not work with ts import as | Bug | vue version 3 4 21 link to minimal reproduction enqfuslowzaq rxlqmpbxtnaqarughoacaiag yqjdpg1ret2ympovw7y4ewqmk5zflezjulpvfgshundextl1thphhga0nkpsojp95xesmvqiy2npyqzjhmclkwuiidlqdt2ninlnaq 82nrkwp4jqlwqsnoeumv7lwtktgupddjdo9osz4mvs9srm6hiojmw oezjwm9m8vbyhvgng0mqpqecoeysurik6tmi52kdjnjcebptovmcmni5jzircjqx uisxb2sybep5o srh jl14qyp3mlduwap9nlfgzl8h169vwaddq7zkwlwil6j qt4elqolghxdeqqnl7ukj2nq5xqplfzropym2hckidsot4tnhxyee jf4t94ydrx5xhw5xe6fdr4hhkgahfmytnm74iokm4pttv8mvyh0nqtqwhjlazv3jyxsksndowlbglhsoailjzzm88nexotro4pofl iec02wjl7hb9huewp97x0 step to reproduce it look like the follow condition must be meet 1 script setup with typescript 2 be in dev mode 3 import as something 4 try to use v bind shorthand something also be careful with hmr it seem like after the page work once e g because I use the long form the shorthand then seem to work but it really doesn t as demonstrate after a server restart what be expect work just like something something what be actually happen something prop be bind to undefined see repro link you can make it work by switch to long form system info shell not relevant see sfc playground repro any additional comment it be clear in sfc repro that api be omit from return state by sfc compiler const return mycomp if you switch the playground to prod mode the result be actually correct and work return openblock createblock mycomp api api somehow it also seem to work in js so I suspect this be ts remove import that be not use at all or only in type position but as my repro show add console log something properly preserve the import in js output but the sfc bind be still compile incorrectly so something else be go on |
vuejscore | vue 3 v model bug | Bug | vue version 3 2 47 link to minimal reproduction enp9uslowzaq rxlqikvsgkcu0krfvvqdgubr19cokldhnvyeoqi dtjhy6hqje xep3bhf0ueu09uannlel4dorc87rgzo80co40hedfeljzvrdltf6ysstpzlwkcbwzbr05hp0yjvcso0dkkkcizkdky5jqokobkrcviqb1bwmbpe2hfawug8gndza3ln0zreye7yed8qzisqgrocg0ajwgiiqfh0z67oyro zdffkeqzkfjvmgzvxnqokvwrucgrs6ef8eg0i xskf9ccdcngmxytz0cn0tf1fhtvve43vkm8v1is0vi1mgswr9pxbmzozkgfteii9fmsowc8jhd8uyby ws sdvamfpmwijpgdg9nlzmim8 lrdf9v7exl6 g 4z4dvgapmqcbe9erjd2ks mxcrfwgx9aedbb9lusowgwdlhp6p4m57pvd evu3v4j58s9r arxj1a8 step to reproduce 1 input type number v model 2 01 oninput 3 v model 1 what be expect input 1 what be actually happen input 01 system info no response any additional comment no response |
vuejscore | fix compiler core shorthand of be doesn t work in dynamic component | Bug | close 10469 |
vuejscore | lose test coverage in 3 4 3 on with v if and v model | Bug | vue version 3 4 3 link to minimal reproduction 3 4 3 step to reproduce checkout the repo above and switch between master and 3 4 2 I include the generate coverage report so there be initially nothing to run what be expect report in master 3 4 3 show essentially the same coverage as in 3 4 2 branch what be actually happen while update from vue 3 3 to 3 4 I lose 800 line of code coverage further investigation show that this be in general only 4 specific vue sfc all of they have a own test file and the 3 3 coverage result seem to be more reasonable bisecting the update I finally find the 3 4 2 to 3 4 3 update step to cause the issue run the matching test for one of my component give a coverage of this component on 3 4 2 76 47 statement 195 255 50 branch 1 2 0 function 0 14 76 47 line 195 255 on 3 4 3 37 64 statement 96 255 50 branch 1 2 0 function 0 14 37 64 line 96 255 essentially the whole script block and the beginning of the template have no coverage after a certain point everything seem fine in 3 out of my 4 component the coverage be start right after the v model of a which also have v if move the v if to the container be fix the issue in my project template code like the below be cause the issue |
vuejscore | definemodel value de synchronize between parent and child if update handler be not provide | Documentation | vue version 3 4 15 link to minimal reproduction enqlvulp20au itt9wbi2fzfl01nrfkordqwaerjl4nnxrmytbmeujt 3jfjjnghlbi3z1u 721ezd mkeybslfwuczy44kdh8y4vlwabt1zeattsirtqyxzq9o97xvdmzzmpsjk iihor5wjvbooytlwonhs6snoy6r9r0nciamq4pfmohysqjkdhfiwychaqt1gc9ckmeogl9sc8otlbn3xlxexcwo4rbei3phm2q9satsvhli1fckek8vydzriqa2vtftk4b0uauyuw8cpeungeecxdyrradgtkuauoekzj8kok6zrgttrxzyny33t0nlricv77obrs3xb1ujcvwkypttyotb iwtsy0uj43gzd2wfzb109dry1r7lklijbigbsez bzgx2exz2xs8i4yqf1vs1lpyyboyu8dfkqyn0dzydzncc6pkw6dvjj i2herxsuzkyksaimpzq 62zmvxgjsmyyqjfmzee2uoblzwr5gmaldth enkm5clr8bx48q3eafn9eqfo5hor7x1yjfjnh708jqrnyhmkwsccfw elbdb7i3ds wx bjwsyyld7ixu95ufaxb nhs7l joe7todhuch3 k8ni5m7indno7nbib91dr rsqklwk4cntgxfqs u 8adfm uod1brbrxgviknbyhyuzmtkmayp5dqvsz9rhn czdphhqbk0qak3vspapixf0x6l bpeooopvcx0kd1zv4dndwwyw5qrsio8 ttoijgtu0sb8b2v51knkygs 81skxsl 4syi mvaves0gy19ae36 g e0bgczllhv1wybhs90 ej jojkspiulfvvqpu71mpst95dr l5 pwcgsimjjlcs v majizg step to reproduce provide a prop value but no update handler for a v model prop on a child component use definemodel to reproduce in the example click the middle toggle child button what be expect prop be not typically consider writable and definemodel emulate a prop emit pair so write to the value should not have a direct effect since the parent component have provide a value that value be the one that should be use this enqlvclu2zaq zwpwtqk4nih3flbajp4kkjlkas9vd3q0thmqpecsdkxav97z6gl3uiw7u3kvfnem hoofpufl1fidf5nhcplyuhh74sromwewgsh2ewoiu1tk3joupqzofwdmnyojb0 nzgugxpdgq08 qqmqpv6saaaoyckfa2xbocbao mgzvdmlqryqiwujgm u8egngierhb7dcivag8ml91lpooasdcmtqhv5myagjxb61veoup6eln4bdzl0yqiwg92b2uwhvfeh cq8fwavnwvcyixzm4mqgivqjciac3b pxcyrklrxp5bzjjoff um7jfin9dilpyau4gfcxhrwom30omcryparltcpmykpk 7qbi1jfbxv9hdyol0bmuruztgtl9k7qqt0ulyhgac0ej2aukasghbmea kyugzqwxe33f qg y15irqrdzspuznrptij6te8m5g7lxeswh0vvkr5tajzcba2caxm8no444ntnvfphnpha cp7onvkujgoko7wcrqbv7ygfrkpl77hk 03rpjplir ojxfp1rjddyws7k0iwnxkj2ojxb6ug9gz951k4hxyuych3wsutpmhv0gvwxcs96z8ev0wtssvkbx7yjs1p6zlpais5lyy26plugdipdfv9dwaqfzu9woh1pp5j63ext7a6eq0ftz3aqnfjkuziu2ixdw7fffxgof8yoflqwhlxeqfxgk5j8 mu1vupak234mr1c lnttxs7tj1f7lc 8l6yvdt7jbe7lol4biajbxsvelldilevsvxxq isrpuqhqsh12kjnuusehklvoez8zyay whejihzzest92lns5 8hxwzoxqvgizjkcssrfqllaxcidvbskpxc3k xvotiqbpky1pa0gkrnjpx270oavi68blcommjdub4vyedvodafq4gn fqljsymbd3crtevsx ft5vyqbgm9bs0loob b78dliludbp m4h6rkspm2vooz9w xd4e3v1resikvelrth6n45mup4 demonstrate what I think be the expect behavior since this be how v model s be document under the hood to work under the hood omit the update event handler should tell the child component that the parent do not care if the child want to update the value and the event update should be ignore what be actually happen after initialization the value behave like a local ref and ignore the value provide by the parent unless it change system info shell system os linux 6 6 arch linux cpu 8 x64 intel r core tm i7 10610u cpu 1 80ghz memory 2 11 gb 30 98 gb container yes shell 5 2 26 bin bash binary node 18 14 2 nvm version node v18 14 2 bin node yarn 4 1 0 usr bin yarn npm 9 5 0 nvm version node v18 14 2 bin npm pnpm 8 6 0 usr bin pnpm npmpackage vue 3 4 15 3 4 15 any additional comment no response |
vuejscore | mismatch child node count in patchblockchildren when render component return render function in jsx from compute with | Duplicate | vue version 3 4 18 link to minimal reproduction step to reproduce click the toggle flag button what be expect no exception be throw what be actually happen typeerror can not read property of undefined read el at patchblockchildren chunk evmnrhzz js v f93e5a51 7163 18 at processfragment chunk evmnrhzz js v f93e5a51 7266 9 at patch chunk evmnrhzz js v f93e5a51 6758 9 at reactiveeffect componentupdatefn as fn chunk evmnrhzz js v f93e5a51 7542 9 at reactiveeffect run chunk evmnrhzz js v f93e5a51 227 19 at instance update chunk evmnrhzz js v f93e5a51 7586 17 at callwitherrorhandle chunk evmnrhzz js v f93e5a51 1667 32 at flushjob chunk evmnrhzz js v f93e5a51 1874 9 system info no response any additional comment by add a breakpoint just before the exception be throw l968 we can see the length of two child param be mismatch oldchildren length will always be less one than the newchildren length image the be return a render function h within compute to dynamically build element by the component prop l175 l296 l329 l337 the follow approach will prevent this exception remove v if flag from diff remove scope slot prop renderer and render they in the fallback content of slot instead of the slot usage in parent component diff diff remove compute from renderer diff const flag ref true const renderer compute const renderer flag value false lead to click the button will not re create vnode from renderer but if the initial value of flag be true its reactivity will somehow be resume diff const flag ref true const flag ref false replace the component that be base on a render function with any other component use plain |
vuejscore | definecomponent prop type be break in functional signature mode | Bug | vue version 3 3 8 link to minimal reproduction enrvu1fv0zaq isnv6yt1kswf9s1zycgba8mqd9mqcg5zh7o2bkdrqjqf fs0jjey9rrxpl4vu9833132yk31mabfsvmzh3pla3gmbqwdeh1qorgpvhkuo01lsa701hyo9paszbhq0w9urjg79uwqweprq5mseg3rvjx43r9ahyqj2aduhnocwd4 nreeznkpqv75hneav km1zcglqrorvzhritnsqakurouxrdtq3kehc1g4rernda3h9msebapdvey1ssfz0qv pbgjpis0opbonshlfqubpdb199 yrb j6cjalazexhwc ojw6jxo72tqwkzfd4se2hzliieuwvtghjh5qkqinzn hsso3rsv 1 k uexae8itt2cxdcht78ebg7kdctajuwxbsgp3f2r njdvezf7r6vtu8yex6hy1npxgvdd4egarc9dkb 64 qb7u1gsyzke1gqd2tqbdcb6gdywbb5mc7ivmcmfzzdldlgtndhpu9jrvnta0biw3ll gwlxypoyik6rukunywhdtrbjl5mwu5acanbameas cte5rwl6icz9m30pzp3vcczi674pt4s4yvpg9zuivxo4qsfvnuu1q8 ggyayvnrni 5zmcdugbkjunyeo57 8alaehiq step to reproduce I have basically take an example from the doc function signature and simplify it a bit vue what be expect I expect the type of this component after import to be the follow typescript import comp from comp vue type temp typeof comp type temp prop msg t list t any what be actually happen any be replace the t parameter typescript import comp from comp vue type temp typeof comp type temp prop msg any list any any system info no response any additional comment a workaround be cast prop to never vue then typeof comp return expect type |
vuejscore | bind a css variable in a component that use a ref on a loop of a custom component break hot module reload | Duplicate | vue version 3 3 8 link to minimal reproduction step to reproduce 1 run npm run dev to start the dev server 2 open browser to dev server and open the developer console 3 comment out the console log line in bar vue and save to trigger hot module reload 4 observe the error uncaught in promise typeerror fail to execute observe on mutationobserver parameter 1 be not of type node this appear to happen in the usecssvar l17 helper function specifically inside the onmounte l42 callback at the line l44 as see below in the bundle js ob observe instance subtree el parentnode childlist true what be expect no error occur when hot reloading what be actually happen error occur when hot reloading system info no response any additional comment I have find that two circumstance need to exist for this error to appear 1 for some custom component a the component be give a v for prop to render it multiple time b the component be give a ref prop to put the array of component in and c the name pass into ref be define as a ref in |
vuejscore | attribute inheritance break when comment in template root | Bug | vue version 3 3 8 link to minimal reproduction enp9usfowzam ruvl4k0rkk7bd0kqjoaaycyxcwx0xlbrppestqgqv47tkq7hybb n6z wynztfgja4vsgnlxwgf8edqv2bolsinth5qslibbjzwl5cqnompw12ah3yuhsbusqzccvvo5tyubguzkh r3kgugt60letbcslvnrxtqbefhksjvx4pash3v o6jslnk2curvqou3k4pkveo5xxrjxnlrwnop8lkfbcs20n8c4rnhiggunyrg ahsw7crcr29heauwd16fgycunkgifjbfknrmjrczwkzl raxbyscdnixw ljf3zvjghj7nmiq3taznror wwfusvxh xso epoeqsep ybd0wlbbyyu7qdsabj potv7ecohtku3ohpurhsqga3kjuo5o5uf f01 snuedsoevw1tmxu3uhnnm5nadmdnavazonkq5q22foc4gngktwnglcsa8 p03wdu53amq step to reproduce create a component with a comment in template root vue use the component vue what be expect image what be actually happen image system info no response any additional comment no response |
vuejscore | definemodel ignore ts type | Bug | vue version 3 3 8 link to minimal reproduction enqfustowzaq jxflxapnek9vwklqjuaiycawcwxnn2mky5 t vgkqv6dtundqtxo9s7semc9w7mtrycbj2zmupubujuw6lwgkcliwpmzne25lcutjimadc6hgavrffsorndrz6rslc7zmalrejyzlrnmlbqoklvajdzq752jeaqelbglg94hl2ns9qzofdistmgcugsqro6ndr2lmyznkipoblc5qtqcbckkmjniieutrpwnsd71xpbfcg2vpbnrumxzttwlqhojxunaobtdzakxkbsxy4g543gww mv5s8 4gu7drhntwytmg3n3heumww6lp7dx ow7h1j2r2g7d io7rk kcxttv1ckgy9 ki2otoqsmlbzvbopr2n1qqgjkbmm8zori 7rfrp wohqnyx2vdv7hz858l ba5wpkycy k9gkxpcsrakxwgziibyb9nuctl0lqmvdkycan a b8g0psqm9a eqmxsmv7w af3xkgv c5p3e9v5lg step to reproduce create a component with a definemodel that get multiple type use the component observe warn image what be expect expect be that the component accept the string without any error what be actually happen the component throw a warning that it get pass a string instead a boolean system info no response any additional comment I m now definemodel be an experimental feature but I guess the user would expect that it work as the usual prop type definition that throw no warning |
vuejscore | feat compiler allow flexible spacing in v for | Bug | close 6499 this pr introduce a new feature that allow for more flexible spacing in the v for previously space around of be require but with this change it be now possible to write v for without the space |
vuejscore | fix transitiongroup avoid set transition hook for comment node and text node | Bug | close 5168 close 7898 close 9067 close 4621 close 4622 close 5153 the root cause of the above issue be the same the element inside transitiongroup be comment node or text node we can t apply the transition to they |
vuejscore | transition custom appear active to class stay on the element after transition end | Bug | vue version 3 2 20 link to minimal reproduction enp9vetu2zaqvqrbliwdjpqm6earjszbfi3qd5ostwgkkayeigwschqywrebxqj3a8 r4ueyuxqxdigz8zicz5vz08uui3c90jrmulbnz4gg03ebxdrtj5uhe6kgwt0pjnrjgilwunysvtbqkpfusrzkgfcxm 5kdkedj dysm4xf7kopndoeyufynp6jcrgnswnw5ajksptu2oklqjivhfwl8l6q a5io5evgo8h7u15gjel4tmoutrcr1xsps7qhvvg1ep faw bwxoxqmtb1nblai2x1vjetg 1b2ggcdqnvoj8okrk9ltgoea9vbv5cqfn38 vh9z89fweld2hdivjy7d7c 7fbqilhrhvwsbpsesq4dzh93svpi5cvcndu45kxrngndldlhtjdd7urls5foml90r9rmply8foqfjdrluhmikzkefprz4gppkqoczdo8c3ui8v kfnzxc8mlssmbqqqwqspaplccfqtnvtupots97yyxaj ka5k5gjqwzslp e4tybr8bde6xd9pv9rojfdv1pgdlgjz7fzktjbt13bqxzrrsoc09usynnqqnz46ns3xatixwyge 6n 0ipv5fsrag3kvny2yfa1gg uf0ma55nyyvlnip6fem30jl3nkypu otm9qrzkx7wc1wi o7ftmywpqepcz jw6fu5y261dsp4r7hp 7e1htrgiyvlsfdk1we2uxr4fyttniqt3jcw7hxnl2ohzpisda4uywj4ekcsolznnbs pai r6zcqrhsxdmajxc6mxtjutnxkqrrikpmcxddvhzzptc4tbarhheu6 x ho7 polox0ggs ig4sku65 g rkspxqmwlhf8dsuq bi9eyxhjg3ckunwmrugrskuiuutahm4mx9kzhv85 31c step to reproduce when use the transition component add the property apper true and add the property appeartoclass to wrap a component that use the v show directive in the component default to false and then when the component be initialize change v show true and the class add by the appeartoclass property will not disappear on the node all the time what be expect correct what be actually happen the appeartoclass property remain system info no response any additional comment no response |
vuejscore | fix runtime core do not fire lifecycle hook during unmounte | Bug | close 9264 8898 9617 the root cause be mount hook be already queue in pendingpostflushcbs and isunmounte be false we can t change instance isunmounte true to synchronous perform because it could be a breaking change |
vuejscore | slot vue custom element child within async vue custom element error during instance creation | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce wait for the app to boot and open the browser console error occur before the slotted component s vue instance be fully create what be expect the slot component s vue instance be create and mount without error what be actually happen before the async component s vue instance be fully create the slot component attempt to create its own result in this error uncaught typeerror can not read property of null reading provide at vnode ce vue js v 974b663c 9664 50 at createcomponentinstance vue js v 974b663c 8543 11 at mountcomponent vue js v 974b663c 6978 47 at processcomponent vue js v 974b663c 6963 9 at patch vue js v 974b663c 6436 11 at object render2 as render vue js v 974b663c 7730 7 at render vue js v 974b663c 10516 20 at vuecustomelement update vue js v 974b663c 9628 5 at resolve2 vue js v 974b663c 9565 12 at vuecustomelement resolvedef vue js v 974b663c 9571 7 this occur if the slot component be async as well and when it s not the first element within the slot ie nest in a div system info no response any additional comment no response |
vuejscore | use slot content with v if and same dom element lead to patch error | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce 1 create a child element with the follow template vue 2 create a parent component with the follow code vue what be expect after 3 second the slot content get replace with after 123 what be actually happen a error get throw and the default slot content get render system info no response any additional comment no response |
vuejscore | typeerror dynamic css on dynamically import component | Bug | vue version 3 3 4 link to minimal reproduction vue playground link enq1v21p40yq iulpxrhyjknnfrftykgprjx9tgbui8y6yy9ayoztny3cwma 96zfbfjo7txwkkxd f1mwdml1102rbjekwjnjqkgletjilkvuvqnd3mpjhnrfq2dzfkirks8p8b gkusblgzzjkutlpbac1lpopyxkrgiykww6frmpijhy8vvyutdkxnp56mzecz07 4jnfvzlfkfy z6jxua4byyo9cnwnfprmm5clbolej35vr1 h5 7rsmuynej0ich4khtz1rmk8ivy035yawffz1mke7h9f5dfzaia04ltj8arfjdmonpiuahgvbfmerqoasovw1kbdehswztxdbp5qnykx1gtlog80uj5yp1jvghkpnmqkf8dvm5p5vybsr19fv2jvsc721w25aog6vc2r6ho6hxgqmxovqyesam5fe2figeafspoxyrlwiafgalkxslnevqfyfxw6j7cd8khpzexpaa4qckkpk8tn5vyhber ksvgdqbywcghmvrv6iecaecinc6 5zkhsnpvi5sueccbesmr 6re3kslk6pswpez469dnag3glw4kdaouw4qai8kqntdzuc8awklcekpiuk0voxzyxn6t62omm8uhul6lvsopvcyutgqldqblsk0s7mz960itrbaygr1pnya9nogenkgh9ys2obmm79vtmzmbiv1enowujgtnuolzf9pibg7vgl6wtg4xgzzyfzxhwhedkbhcjwomb8wqmaqbm19zrggprio9n3xnnkzhz4xkbfnqu4uagmegkskk5cqo1oevgyc1rib7prhrvjp5ycj s2pgsgskvlowzjj84zc fww5tvmlhapjzryt vfxsgjohwdak738lbyposyohjhxd2rc87rai30el1ttgeu7y8ifaxr0bk2gp5t7myqqa sugqrzty71ozhamz2lxqavrndoa3fqtxeg 54olcp0opcdzzaoa49acxypsvmhige 27ja2raoo cfq c av1 va0xwx3kzv1a0xyovoodrywwrzjxx1r9q csj0xsc5w2mdtfkeb5bckoyjujyshfsl3szpoqgf0yer10 lycum0roberfoa0l5w5gun4mgpvh0jcdvs21qoradw5kwo4kienfmb7uil5mo08 wmc0cm8udahqq532p4momx4z8yohgj5higr4r19unulels3ecrobrxf fg xlarygurhge2xmtzkrnogokeh6kyb6br lss5zshjdudgazyr8ioqfmlrudz9h5sfc3g5ythmkjdbjepz wtyjmlzikeiwv6nbgocqgvbitkbwqiq62anyhmr10jzvd9md1g5vh ihuxg8sggw0u6osqf3mtqd0ritq0ep3s9xnpphhyxc0ibdjosbsjveqvzsxehqa gpenft2ne55lv4176cm6rfkxgmkocq1lyej0pfaihmlum9yw3d67 t b0 gdcamtcdxzh4irkimoss jkoxb04stzmqf4kcbdwzxfe8ky3rm igu2kjgchc2yyvqlegf6xuimtwkcrfhtxwjqcvabiptba80b qoviaewtzgbllur by5u3icgeitwrt8bfdpdnzbpgf n7s7n35bfta kkvxegiwlhp nxwmcw0b3ctejtntr8wex7b1ouweojv4qru2ovwixmvroznsph rwgevywal x4mjsw9k0 jfgnju usb90rxwju uhgoufvwv yznrum70 wfun 8pni6xeskvumqwmuwe2vz2faycu9njzawdbigexapzmhht1vdi7rrv7075z nn9c1bn7ge 6ohtpmbdeobpy p84r6ddzbiz65gzj z au996f8 simplify enp9ve1zmzaq ssqh5jmohdizxuybdn0jj20mtphlgqvherijd6wmwz vu swcrnwwlp9 0 7cfro69tm3swolw01owqw8m0gdsynovqkoumzqlrtnrnk5vhpvnultkun8utg1ipzmoycpas jw53rvsjkykdsexyo7rm6vpxmojm42rio6hktrfjc4 t dmbtayl73v1aovpzy6kgmnoe25y ifl3a b7mngmwaspmdx1yfw8pir5fgud7 muuisu8jlfs8mv bcuovz4hxmlhq5t46xsjwjgwodd5qmbcfvs66kfdvv4aznjbf6acuwrdrmwyzmbikzkk0oti2qgvlvnh5icvqeuybrsokkn6ydyecv09awtachq03lc0m4mbz tmyg3pec18wla mygn188p mzen7wyzhof naricbovo dx97s7qeveoilozmbfyckwblwagot0xilaypqqpkyr5fllgxnzd8yiqjztzun9bl0j0pfv2i4syjmxu5 zihlvrge80tfyzv3z3rv7rloxpem1whqjpvjvuummg83v2ip 8nyyk3l8p7a icwg9zxdg7f0fvqnvl5tnd xgtrpejbvsghx0c5oscr8vtz88htj3qvk0upq9nrxxgfthcwnd5swqu6v7lvsy9tsc7vfno8trrig6na7sazinxyg5lepaztwxido i356mr020uwmfzrtet5e6ibjfmfyawnlyfr21emxwygza2uekokmduwls7ekzfnvynlx9vnvxww6i21l11wi2y5vxdbbi4vghorjlbusbxobkkwmwckyugomfudf7v 9kwcdp79lsqp1i0vsnpuuialz1liqeezkohwuoclimyiv5hgpdfl7xtstlnmtzdjkynschozge0bzkdcplw005vjxz0ucuyizbjwi qutvfewzhqe484bfoyblc53lnorybdog rmnfr3qgdg step to reproduce npm install npm run dev what be expect I d expect no typeerror s and that the component be properly mount and have my dynamic class what be actually happen open your browser console and you should be greet by a typeerror typeerror fail to execute observe on mutationobserver parameter 1 be not of type node system info no response any additional comment if you comment out the follow part in the foo component you get no error hover link pad v bind binding pad px or if you remove the class from the component class loading classa classb |
vuejscore | the div which have the ref attribute inside the v for when I v if toggle they the ref value length increase more and more | Bug | vue version 3 2 47 link to minimal reproduction enqtvutv00aq iudossv0qsot9qttnadsdxeerfmwbunzjab3du 3esr zuz68r2nniglr6a3z1v5pu3n9g1uupsytsnypnppiwyte4bt0vxmutwjnfvithssw1haxpni qxzpavoaippksnloyjyorsuxb6tg02hwpmwi5hqmyhjyh3blrzcsatcppsbehejowxwmxpztg9r7j0zeorhz4kyuyeuuobvhyfxy1meakbrecrnc5t7rzqq95tiqqwg x youde2rpsymc50ttyl1rtwh2tvxrvrx t3x7snisz1esmzscal4aphoahhosjb2zzhsfs91jnokb9qkjoqsh9eieaeqzxpyhgrnahuqavtnva 6wuxhe0rurldv8csj9hxa6hyanxh7knmnk0 m im7murr23ufsh5 hpdtcfz3g3zyiabextzbyoxnafazcdvpg7p211dzvms6yhw rbhdrpvfu8asgk3llc upm5fmw5hetdxmyiq59cwh6lzayrgv0yrw1pyatej17hbsuylivld4htxh6tfpug3bcbbxo9ta92lv1eflgtcx6livap2u96iot2dsk6vhwz6ngikcv2cn9avnrdnd4nozh1e6d0ombjgab435t2b3p3jsmby4baomkwrz3yrjapysowh1qkjfi1p7nmszvowfjbs0g8owssk 4xhh vx5xura1mi1crklnmvht hn76zr7j2by7z44v3b0cbp6fbno0fduh0amu11gbyw3959wrwdg fs5s5x7rnhd6ryoe9jdbtxiie3o7jg7cewlkmjfpjbluvhdkf5rz2ycvgkohxtc 630ft3z8fnqy wlwwx2e 7 vs 6wkosem6wnweqwb6uiyzxhqdle 6lt52udjx9it1r vz24c step to reproduce if I click togglevisible many time 1 the refdivsingle toggle between null and div 2 the refcompsingle toggle between null and 3 the refdivarr length increase more and more error here 4 the refcomparr length toggle between 3 and 0 if I use ref function it don t get null what be expect the refdivarr length should toggle between 3 and 0 same as the refcomparr length what be actually happen the refdivarr length increase more and more system info no response any additional comment no response |
vuejscore | hydration error with r in text 23234 | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce 1 git clone 2 pnpm I 3 pnpm dev 4 visit what be expect no hydration error what be actually happen you will see a hydration error the issue be r on server not match on client screenshot from 2023 09 15 14 35 54 system info no response any additional comment no response |
vuejscore | fix runtime core cleanup hoist vnode when unmount component | Bug | close 5256 note disable vue devtool first if you want to test on playground |
vuejscore | a comment in a template may cause an error under certain condition | Bug | vue version b775b71 link to minimal reproduction dev enqnvu2t2zym suoera9449k9 babtm2h 2hzar7s zas9cgwyluscprj8f vy klmmjk4kvfon3qbb4ae ju7qe7xtolsnkzkbwjiy7pqzsqod1mjibjptuyarwxtgjdbd0psloikagjtrth7qq2 35wi 8v5ht5y4105 ccvrdqsg5zn8uytoj1fmvcx3362wdztsnt8q0so5ysibtyduepsq0hk1bmpahw2fezzb7hrzv8hbcdhinyrmqivpavbcl48qch7uuvivnomqx6rfnjr1 ahhchlvg4wmtn3rkfdfiqbksdhastarmlkxf7mpzpfchhsl pq9imrtchmxy6nlp3hck8sgr1o0br etlyrzn5ns zs3e0rfmel5xpqniogevj1ttvrekqkawabtl4gjk6lvrnfok otk2x2gkiproskx1x0u1pebocdtm16zvapn6hsy5bpcy bucw0chy 7kzpaullwie9 adfex5dsprzxmuj 4ncjdok0bmdapzlpe1nsgaswtfrdxvk2xgaqojvaqce0bnfz7i0fjt757kxckg zwb0unad5vwyuo6ttchdvbfyu6yy2bhtkndsswlhossaq7pz0mkg1nahhlhb7b4ib3fvka82vqgn8hm1n0zrk1bsiz nn61wanygutrbjlus2fxtowmlpckyqthboed9 lfycwb5vexnnzh7ubh 2r78xpp8goby7hgbzuaeewyxze zsp o6mlc6beujvgd96ftc xgj7hv2isae4eo1dmcsycy 2 cgxspdl ua98hzwshddplhfunof7v38pvdqg8jizub5yxed91i8qhtub wvoyu5iami8r2cx joxdwl2dzcdzyomobjw sesb5k2pbqjxivw g7weodxtpw2qzg6kdwdcphtcyjwgxedgig4lcau9uxm pxeaoi6yhwom36k7a6jcq omdzph fedgw5ephvart9jufut79wqgnvnhouswhqafmngx4h8lhoba1vnmuydhp3zlipzllememogi6d2ev4huzfdq0uiom1p8aatjvzxurvjtvf8drr860yvvnuzwql0q qs3wmpyyy av8g9coomir0zxwbbozv8dp3v8lw step to reproduce 1 open the reproduction link 2 click update item button in the preview area 3 you will see an error 4 delete the comment on l26 in app vue 5 do step 2 again 6 you will not see the error what be expect no error occur with or without comment what be actually happen a comment in a template may cause an error under certain condition system info no response any additional comment no response |
vuejscore | defineprop fail with import export as type | Bug | vue version 3 3 4 link to minimal reproduction enqnu01v00aq sullymo9gqvu rgbvqjoeaflbj4yuyjs8x7ozlxgmt5vzo7dsged3hzvpl67816zf6guowhynzzsq2awiqah6d62nxxvczuzzvkgrs8shovwlznaoveqpw0ru6pz6omdf8tab2zheyysuxlwtgab3foa5wppkjfm4unmdt4r6wsdeo6zr9yvyg 9 qzx759spksus uhigeddb0nynespw755txtm3tvgqjempcgfjtc tb6ewg5jooup 6s8tspp7bohqp5j14mmbu6pgq6wuvkiij2hhx2y450frrpnxsjvpnhgshrf2w kbkna6ojyw89fbmqrgqxujwec hasjmx9a eqamqbllxrot4b4wrxdjepb 1561lvefpx5bh7dplzvefca5x9z0z5y03gbta34iborev1hty7ke3ywmcyctlmyhzdc 4a90mdxdisrmc 1cywc8p28 vyedfj scs6hp57hl8mpql4fise57nxgwqg9qets36ylg9fd0 2bwdepuzfocipvp3u8 of0n3tf7awl6zuziyfwsd9irfr69vlmxwrncugatsjgorkxkzu a1hfnfi step to reproduce 1 define some type in a file type ts typescript export type prop prop string 2a import those type with as type notation and use they in defineprop app vue typescript import as type from type defineprop 2b re export they with as type import they normally and use they in defineprop index ts typescript export as type from type app vue typescript import type from index defineprop what be expect the component would compile normally what be actually happen compilation fail with error vue compiler sfc unresolvable type reference or unsupported build in utility type src app vue 3 import as type from type 4 5 defineprop 6 7 const msg ref hello world at scriptcompilecontext error at innerresolvetypeelement at resolvetypeelement system info any additional comment shell import as type from type export type doesn t work either the use case be to export the type of component in a library as a single namespace I couldn t find what the actual thing you get from do import export as type be call in typescript so you would be able to do import mycomponent mycomponenttype from my component |
vuejscore | inconsistent component ref when use defineexpose | Bug | vue version 3 3 4 link to minimal reproduction enrvvetv2zam iuel3gbxmbanti36b4f1mfyi67ylr54nv3ozemq5drflv8 snjso2mbpq 9cbifij yi9fbaymjzyfbpeh0rhppqkppjlcmv6dpyhqalfletfioa2tqwe7hljn5drsolwhhqt6tncvb0cpehsx2yt fvbrpvzampl9joxfk sde qq8f1x7j8grm2ssx8cptsk5iexgc7y5l5gyoktp7bbwa3jh2ck05xh94rinr39mivxm7ahof7booyanixhgtfrhgnwuvdxwctr7kyv6nkzgsuq 6ktqoxok312ef 40uye6wyiuwdycpzx5gtg8xmeofuqdwn3gho bpf4hci g9y wzrenm elqcxwvayzkb9qujorggjgapgpugfjinei2ocbpgdy4bzh87hb85wyr2tebc9maaeqbm2k9gtfpwmwxut7ru0ehnfrisjptp3gttgsd2p47zg5fyga5yq4mhiltv4jmxi1xhttdgrrht2ep1el oi0wyojlc3s29k3glu9ekatadhyhiuuc0u8oi6ox417j7bmpse6ic8jb6hhlfrjkaglk21vxjlh4ahupsmoyapspnrhe8 ojlrhe6w5dxm3x r3 qvx3sl0gu2wg8yvahxapoyxnf9p2xf0bg du8or5hi2nkcvdmbjheu9sdozxvhokzdckppvwa53okyibpqohvxd0utp6a pevvhlrxuxb y9uo1qwbhcsck7bhblwz5qiw0nob3dn8dtoowmhhzfr4exwgitsx4xdjtpdfmtah3zvhmtgnvj0y0f0jbvivtxtjqyhgi3s4zp8j4q2ftzy0el2dw1p wi nty bkoy step to reproduce the expose vue instance when add a ref to a vue component in script setup differ if you have define expose with defineexpose create two component which take a single prop identical except that one have a defineexpose import these component in a parent component and set a ref on they then log that ref s value myprop in a watcher or onmounte what be expect the two log log the same value what be actually happen if you do not have a defineexpose in your component a parent component can access the prop send to that component via myref value myprop but as soon as you define expose in the component myref value myprop return undefined system info no response any additional comment the documentation for defineexpose defineexpose doesn t mention anything about that use it change the behaviour of other property on the ref so either it seem the documentation be unclear and need to be clarify or it be indeed a bug |
vuejscore | innerhtml set from render function go missing when patch | Bug | vue version 3 3 4 link to minimal reproduction enqvvetvm0aq ittlissdyf2heiapo3ud6smpzuecizdjrbldwfhkcv 7 wuyjyxwkuwz fxzfpznnjtttg6wyajuskmrxpc40wcpjcdkzkwxiqzfluobo6yomqajuaf 2tb8xyl9v0awp sbsqmiyhw3sd2frp7di 3vjuto10kwsbs7tgyyfqjkvgzmky7y9mvfvtu1gnchyecko1tnook8axifppci5zyfk2rnmewqgx0snkqgzdbciels 1kuozxbm5k7hxdiwu8q5mcfttwq5koistmkal7rfwuoauw8gh9wlqsj1maxiyhesevnlt0lkd9pbhxrkqxko9wsiguyi5elfrtvgsp 8qssamfjxqby0jju0wch4plav5xavbj05huhstceyfxc0j muzsbo k7rof5jfkw2yvuvkjefnx fdcutsvflv7p3m8yfaftd2rq922knsy575ueq ecgl tvhtnbeeoznmulhsdjvxkzdspptb4r92x00sxxqhmk4ylt y63oj 5brbz74ovsw6g1aq1 avyzftc4duwkzgvkkac7ny6tx 6ytgcuhq0hnng ro xgkc9i8msebjkpvhrfqi9nn ymcppiudmen3hmmp7u fqtv anv2ozcmlgtvqhjlrc8ofwjiev cde h ipxj4ailzwqjuwetvnypr4ur2epvihs1azmhy5gfpspmu v1we1ugc3dz43l98 cxjstncg rdwctvw2lwgnz9 5xgp7n4kteszjdmvhl3mhpbn9 yydt77pag dpmu quqoj4 ok4kcwhcfdirsojfmu2iu yldadjnhgsltncfmgehwxwtbchafplpda3tlfgwrgrxvv gt00h qjeu pb0xnk99z qg utv i9gfhfh step to reproduce when you arrive the inner html provide to the comp s div be visible when the delete be toggle the innerhtml should end up wrap in a del element but instead the content of the div become nothing a workaround can be demonstrate by set key to true in comp vue which will assign different key to the div s which then I think force the element to not try patch between each other what be expect it to work the same with key as without since the key be not suppose to be need what be actually happen element go miss system info shell system os linux 5 15 ubuntu 20 04 6 lts focal fossa cpu 32 x64 amd ryzen 9 5950x 16 core processor memory 65 15 gb 88 39 gb container yes shell 5 0 17 bin bash binary node 18 16 1 nvm version node v18 16 1 bin node npm 9 5 1 nvm version node v18 16 1 bin npm browser chrome 116 0 5845 110 npmpackage vue 3 3 4 3 3 4 any additional comment no response |
vuejscore | hydration not update dom of img src and v html with new client side value | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce I be stumble on problem with certain stuff not get update to new value after hydration use pregenerate site with nuxt 3 see issue with reproduction here after look at it daniel conclude it be a a vue relate problem visible in the reproduction provide in this here issue here be the code js what be expect that the content of the img src attribute and v html get update with the new value of the timestamp ref after hydration what be actually happen the server generate img src attribute and v html stay the same not get update to the new value system info shell system os linux 5 0 undefined cpu 8 x64 intel r core tm i9 9880h cpu 2 30ghz memory 0 byte 0 byte shell 1 0 bin jsh binary node 16 20 0 usr local bin node yarn 1 22 19 usr local bin yarn npm 9 4 2 usr local bin npm pnpm 8 6 10 usr local bin pnpm npmpackage vue 3 3 4 3 3 4 any additional comment no response |
vuejscore | default prop value be not reflect in custom element property | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce two issue with prop inside element define with definecustomelement vue component respect default value configure with ie defineprop but it s not reflect in host property value on creation set value on custom element and remove it afterwards strip default value and return null instead what be expect prop s default be reflect on a host element prop s default be use as a fallback in case value be remove on a host what be actually happen undefined be return instead of prop s default null be return instead of prop s default once ie host s value attribute be set and then remove by a user system info no response any additional comment this be troublesome with form input where input be expect to return empty string as no value and never return null they be actually always convert to so el value null result in value be an empty string |
vuejscore | lifecycle hook be execute in the wrong order | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce 1 click the open 0 button 2 click the close button 3 click the open 1 button what be expect console log open 0 init onbeforemount onbeforemount onmounte onmounte onbeforeunmount onbeforeunmount onunmounte close init onbeforemount onbeforemount onmounte open 1 init onbeforemount onbeforemount onmounte onmounte onbeforeunmount onbeforeunmount onunmounte or open 0 close init onbeforemount onbeforemount onmounte open 1 what be actually happen console log open 0 init onbeforemount onbeforemount onbeforeunmount onbeforeunmount onmounte onmounte onunmounte close init onbeforemount onbeforemount onmounte open 1 init onbeforemount onbeforemount onbeforeunmount onbeforeunmount onmounte onmounte onunmounted system info shell system os macos 13 4 1 cpu 8 arm64 apple m1 memory 83 78 mb 16 00 gb shell 5 9 bin zsh binarie node 16 19 1 opt homebrew bin node yarn 1 22 19 opt homebrew bin yarn npm 8 19 3 opt homebrew bin npm pnpm 8 4 0 opt homebrew bin pnpm browser chrome 115 0 5790 114 safari 16 5 1 any additional comment in this demo item s lifecycle hook be sometimes execute in this order onbeforemount onbeforeunmounte onmounte onunmounted |
vuejscore | scope style attribute not attach to selector key if it s a pseudo class element | Bug | vue version 3 3 9 link to minimal reproduction example enqvvntu00aq zwrx jeybql3bpcrebffhgpkc8ii f6j8mw9e6yl6rvlh9n1m6kxahsvnkzc acmx7pjpkzw1ybk3ey8vgzwxic5gpgsjycvkmp9ssjp1zvmwnxutma89cs32jluxnybidzjodqkru60ksrrtaehppgkciqo62hdwj1uqcc8yfynmmw5lzx0cmvvygrtxkeano8jivpr9ep vt4wrhrvci8qnilrsdtwybkzdl4pgnuyrh0oba5ea1 jcuv8evhqixqam0mltbtcbsyiokajrjgmxcnmdidg dantrv80o4dkrnkgewbeedi7zfuqbshws4i0pcyzpadfqusa8vp3eox0wfovhdeaihbwf92hre9p3te4kvcxhkm syxge2xikz3wht9tlkitd2jmxaq vjxp7vgpaza4trfgecdlr32vwonqyoa20omccrfznvjlqpa0ex9lhzobwd9qjk6hwutipkqkjo9213ydwwqjoswyoblagh7uptkfpkpjsmacuyazznzs9hkdvmplzjwfhe9yi6rxrt wgsxdqgt 1gxbhsdxkmg70xt8zk 0gt6gdets7 qcpw ogovwg nxvfeefl0arewpsxw3iz7 b3slv9n5gfvyw9bzg6yva3a91dgolv4mgdfcaoe4a2wh a xwglx0ge7vrtsx92yadbnpu6bmyseunvz05oodkselroyqad bedlcnoyb0xfzbr299fs65m3a4s5elrh89y 4pbukstw5o98a7qrz5dbnc0s3pkmfnh in6ovrdqpkqrvsx6jhyjeju3z66a4yw7v1wpp69mq1okro7mif8 ttewhsxjb1 cj3dg391j k eihdu4midnstndo6owd byjlpnikmru teuhgwlvwrjkmuk8su kyzkntfzzmlo04nccr19yoy2xhghfptmenxjs6sxtnkmbgau6ew 9iknrkdwvscnpdm8zduo7a2 51ur0okv53m9g99jmsk step to reproduce 1 create a scope style block 2 add a rule set with a selector which have any ancestor selector and a bare pseudo class but not be or where as the key e g div not test not div not test example vue what be expect the generate css rule set s selector list be scope to the key of the selector I e div datum v 7ba5bd90 not test even if the key be a bare pseudo class or pseudo element except in the case of deep css div datum v 7ba5bd90 not test color tomato div datum v 7ba5bd90 require color tomato div datum v 7ba5bd90 require color tomato what be actually happen the generate css rule set s selector list be scope to the last selector part that be not a bare pseudo class I e div datum v 7ba5bd90 not test css div datum v 7ba5bd90 not test color tomato div data v 7ba5bd90 require color tomato div datum v 7ba5bd90 require color tomato this lead to style unintentionally leak out of the scope tree system info shell binary node 19 1 0 c program file nodejs node exe yarn 1 22 19 c program file nodejs yarn cmd npm 9 8 0 dev package node module bin npm cmd pnpm 8 5 1 c program file nodejs pnpm cmd browser edge spartan 44 22621 1992 0 chromium 115 0 1901 183 internet explorer 11 0 22621 1 any additional comment this seem to be true for most pseudo class and pseudo element but isn t true for be where and the special case deep initially post as a question here the current behavior be unexpected to I when write scope style as it easily allow style to leak out of the scope tree e g when use slot |
vuejscore | set a reactive object on a shallowreactive map unwrap the nest ref in the reactive object | Bug | vue version a95e612 current commit after 3 3 4 link to minimal reproduction enqnke1ugzaqha8y8szgoicyreikhqcbbumsedeeyx chqiyfpeocajnk0u2lmfe957he8ihtcu8cfjoateog xghj sgetbwtn6cdcklsejaf0wixzcpzhsxl wbktorqoaygrlgodr1mjnqbke9snmahn2nnv635s1ybcrc4jhj8xnyxh79ybt4gqosoordszunp joj0yzoh6lqpax7he7u7ybuxpgikkaxr2kxu40drpo5gs zwxotnl7g5j6 k2blw0fl4okxsvsakol9uhhgv mdylvkt30hbyml8pcxzyzwnqnkbul5sbspwbwo lva step to reproduce open the example in the console you see the message print twice but once you see the internal ref print the issue only show itself when use set on a shallow reactive map foo2 if you initialize the map with the same value it be correct foo1 what be expect the behavior should be consistent either the shallowreactive map should always resolve the ref or never imo the reactive object in the shallowreactive should behave as normal hence in my example it should always resolve the ref correctly because that s what the reactive be for what be actually happen the behavior be inconsistent depend on if the map be initialize with the value or later set system info shell system os linux 5 15 ubuntu 22 04 1 lts 22 04 1 lts jammy jellyfish cpu 16 x64 amd ryzen 7 pro 6850hs with radeon graphic memory 10 51 gb 15 28 gb container yes shell 5 1 16 bin bash binary node 19 8 1 nvm version node v19 8 1 bin node yarn 3 3 0 usr bin yarn npm 8 19 4 repos packmatic node module bin npm browser chrome 114 0 5735 90 any additional comment I be aware that you should not have reactive object in shallowreactive one d |
vuejscore | vue 3 do not handle event with specific name capture once passive from custom element | Bug | vue version 3 link to minimal reproduction step to reproduce create a sfc component define in that component event with name capture define custom element in window use this custom element in vue 3 app subscribe to event and trigger some method on it what be expect method be trigger on event capture from custom element what be actually happen method be not trigger system info no response any additional comment that custom element work fine with vue 2 |
vuejscore | bug template be not update when pass vnode to dynamic component | Bug | vue version 3 3 1 link to minimal reproduction enpduufugzaq mrkf4iawd2cth1djquhakxjbwzl2kgv4e8dm4q0obgrmz0zdxn7nyybvwb7vgzcsunoem6bq6vkb7r1njevlc3uwt1tamqyqoopubgcwr63oaucuaw4vgm4zlizjniey7kpvosvd1irqpvm6gy6oskcam3guvocxkpkdgchm1eqyjdcsitfid50trpyiipogucsjryvi9e0remz9xhl7 adbpfvojjz i3zl3coed94j m5rnistwihdew ogax rqibdnawhob1nxqgypugmk92ededw 8e802lh4qx06dpr77vlyzijr5y6uoc0h4sxanfqrgts9fr vh8bdiynvynzwirx3nxjmqlhf6 iqzhp7v ftybanx12qlv6trbktsnejng8 qxzhan8uvobglj439h1racevolwfa8qbwka iynbv86hc8o8rxey ornrba step to reproduce click on button what be expect template should update to show str add str add what be actually happen only str outside of div update to show str add that be str str add any additional comment in the space vue file the child in the template be calculate use slot default the content of the first child be str and when it s pass to component be the shapeflag be mark as 1 which prevent it from be update I m not sure if this be a bug or if this approach be unsupported if I wrap the child with the h function there be no issue with update enqfuctugzaq jwvlxcvwb1b2l76azmwhgiygaiggrs1ivx7bxvi49ktdzwzs pzkx12nt9ozkiw9zmsoku9v7o7jkjqulyqgknygiyqznuqa6qzqx2xznwb mb0sxyiriniwtgdoytfs4trohr2isi0yftvckrz kiku6nxhgdqd2mtob3f5owbqmdkrbryx3cervgmq1pf0rffzqup0etvsjre42gwt5g3whahnycibxjrkc1r6pnwchy srrklnhcrneehu4kjiwkdhrshpjhtgre06q6fweoqb4kd8nqnh rvvve1jadvjz3qptos6bnhgv1evqw6dybtndhf5lajcuropdcafwfxcqbh2zcelakspn zotu1 rdb f2o 8fhp14hmjkxlpgmqruxjczlsklu7r07frm nostanhx7qsavhxjyps t3h2t6qmaov aqowuxo5o7zt1oxzxnwpebhlzvqombj2kx3 zwdkxfs gmf7aat there be already a similar issue 4903 that have be resolve but this one be slightly different |
vuejscore | error handling inside the effectscope | Bug | vue version 3 3 1 link to minimal reproduction enqnve2pmzaq ssjlieswbvaw5rew0v76lmhpzsqojaetmbbtkkoef 9448mhcxpt8jp8 hem8hn6iuu6bhhab1tdkeaaucj6euu400nhtlwpprq 9wunsqolohgkbixanmxt fy7gudoxjzmzk6cgkb5ttsqzoy7gsbg6qtwgbcxsgz8diodpohn4wi2rblqsijpldvl8v0qwtoy uxljqwbqgh1imenlzftxgsl1mrofy9yetrmde6y6pnpumw1uputex9cv9zmwjzrhouxerx0qcnlnzqdwtuw1g4bhvsievuaf62gsso 43ubrravsogr9i mfwzw 8dfhvwjhvhzcyqm8vvgmcrluwhhh62zeixgiudfqaq5n3f7efucmxsn15w11y7ccyo9hvtthbgo ggqcympqax5pfp3jh2qjvaa7hyumdh1dhde3xydnqyndgvi9wpqbf0xfe0yw n6z u6qc5 ux2r1f4va1tobnaolvw8x5l28ltejohuijq nag xlsmstt8td1m74 wkjjaexbgq34uu1lvdp3fl6wat0spdnpkzkdbdwfzx3rdxhbys8irgmzvky6 qfg5szmfxk8eshd8fducz htk9v30bpk zox9d8battu fe6clmp0n3lzqmr7dno8 ig3gjwviwo5gsc0rlaatomtotpx56tfve0xlr uak2klofr5q5e8 ocluhvmrwh2422b46qptlku6rfid6aghtxl0e5mp7 npqz3zg1 ahm8eqm step to reproduce just open the reproduction onerrorcapture can handle any comment error except one uncommente what be expect throw error from watch inside the useerroredwatch composable inside effectscope should have be handle by onerrorcapture what be actually happen error not throw but I see warn about unhandled error system info no response any additional comment no response |
vuejscore | why can I just change count and update it in the child component | Bug | vue version 3 2 47 link to minimal reproduction dev enq9ustugzaq bxlf4gscnvwqoqispuf6l3ugyct0ochbjoqqvx713akcklyrdjtzuzozuaevyqvnjugm5ybsjfkisnspwoqgq6ktqhhmu3rgpzachqbnrqh7bfp6wuqel 5xucgoplcwftjtli0divihwuvoqkisn59uwvctavlucouq6lvlypdkbn3bhr3nbvsoe3vntvptbenljcuf8ucbpaomumamfwtw92zx395fcmcae7gk akj5b iccyvfoqawzrtm8ee3nv b75jdehga6syynqlm3dxccnf2hdon6d4mdzsrsvh9ivsv0oda6zsg6i8renif1xdhpixbmqtfkdegk2jqpxuyb3k bspz9gckjxp0evgke4c m4hstvatcyvpmmke6o0weuonkarjqonzwltesbp qxfx4hdwpstj8yw5odll gavckedvztqb5zjrrtnrmm31xbma9epxhn6joe37rgicfct0ygq step to reproduce what be expect I know how to use prop properly but there will be no warning on the console and the datum in the child component will be update normally this be like redeclare the ref result with count alone in the child component and it win t affect the change of count in the parent component what be actually happen it normally modify the count in the child component and be the late value when the count be print without any effect I find that switch to the dev version of the vue sfc playground do have this problem and whenever you switch to prod there be a warning system info no response any additional comment no response |
vuejscore | maximum call stack size exceed in vue warn | Bug | vue version 3 2 47 link to minimal reproduction step to reproduce basically I m try to test vuetify vselect component in vit and I don t have window resizeobserver in jsdom this result in error from watcher vue warn unhandled error during execution of watcher callback after that in node modules vue runtime core dist runtime core cjs js be enter an infinite loop in function warn it take trace which include ref proxy and when try to console warn it it trigger avoid app logic that rely on enumerate key on a component instance warning which then have the same trace which trigger avoid app logic that rely on enumerate key on a component instance which have the same trace and so on loop what be expect no loop what be actually happen loop system info shell system os linux 5 15 ubuntu 22 04 2 lts 22 04 2 lts jammy jellyfish cpu 20 x64 12th gen intel r core tm i9 12900h memory 26 01 gb 31 19 gb container yes shell 5 1 16 bin bash binary node 18 13 0 nvm version node v18 13 0 bin node npm 8 19 3 nvm version node v18 13 0 bin npm browser chrome 112 0 5615 49 npmpackage vue 3 2 47 3 2 47 any additional comment sorry for a bit rush report hopefully it s enough detail I m try to debug it now |
vuejscore | error handler info parameter be number in production string in type | Documentation | vue version link to minimal reproduction step to reproduce app config errorhandler say the info parameter be a string from reproduction link 1 run vite build to build production version 2 run vite preview 3 look at the console it say error info 0 which be a number but should be a string from stratch 1 attach global error handler in the app and log the info into console there 2 add some purposeful error into any vue file 3 build the app for production 4 run the app and look at the console what be expect either the type should be a string number or the runtime version should give a string info what be actually happen type of info be string in developement and number in runtime system info no response any additional comment no response |
vuejscore | boolean prop without a value be not default to true when there be a v bind apply if they begin with on | Bug | vue version 3 2 47 link to minimal reproduction step to reproduce what be expect onsomethe prop should default to true what be actually happen the prop be ignore system info no response any additional comment no response |
vuejscore | whitespace preserve do not work | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce check vite config ts you will find that template compileroption whitespace preserve be set then look at app vue and the output what be expect I be my understanding that with whitespace preserve the output should be image or at least it should be easily possible to change the template so that it be what be actually happen the output be image and I have find no obvious way to get the desire output I have try add a second with a space in it add a with a space in it find that on stackoverflow add after the span add a space inside the which wouldn t be the desire result anyway but it doesn t change the output at all system info shell stackblitz any additional comment I believe the whitespace preserve functionality be add in |
vuejscore | fix compat ensure proper handling of render function from sfc use vue extend fix 7766 | Bug | this only affect compat mode when a sfc use vue extend to define the component script the compiler add the render function as a property on the constructor not the option object in option the same go for internal property add by the sfc compiler like hmrid so when we create a vnode for such a component in compat mode we have to re assign these property to the option object which we then consequently use to create the actual component from if we don t do that we get a template or render function miss error fix 7766 |
vuejscore | vue compat not work with typescript miss template or render function | Bug | vue version 3 2 47 with vue compat 3 2 47 link to minimal reproduction step to reproduce run yarn serve from the root of this project and then open the localhost url that be emit to the command line in a browser what be expect the vue cli starter template application what be actually happen a blank page console show vue runtime esm bundler js fe26 1595 vue warn component be miss template or render function at vue runtime esm bundler js fe26 1595 vue warn component be miss template or render function at system info shell system os window 10 10 0 22621 cpu 16 x64 intel r core tm i9 10885h cpu 2 40ghz memory 8 22 gb 31 75 gb binary node 16 17 0 c program file nodejs node exe yarn 1 22 19 c program file nodejs yarn cmd npm 8 15 0 c program file nodejs npm cmd browser edge spartan 44 22621 1265 0 chromium 110 0 1587 46 internet explorer 11 0 22621 1 npmpackage vue 3 1 0 3 2 47 any additional comment I be try to migrate a vue 2 0 application that I create with the vue cli to vue 3 0 use the migration build and run into issue immediately for this repro I create a new vue js 2 0 application use the vue cli with the follow option vue create vue compat typescript vue cli v5 0 8 please pick a preset manually select feature check the feature need for your project babel ts css pre processor linter choose a version of vue js that you want to start the project with 2 x use class style component syntax no use babel alongside typescript require for modern mode auto detect polyfill transpiling jsx yes pick a css pre processor postcss autoprefixer and css module be support by default sass scss with dart s ass pick a linter formatter config pretty pick additional lint feature lint on save where do you prefer place config for babel eslint etc in dedicated config file save this as a preset for future project no I then start apply the step describe in the migration build documentation this pull request show the change I apply it seem like I be run the migration build at least close to correctly in that 1 the project compile clean 2 the first warning I m see be a deprecation warn but the vue application doesn t successfully mount I m see a blank browser window and no vue code be inject I m pretty sure this isn t the same issue as since I m include the shim mention in that issue I ve try both with just that shim which be what I m show in the repo and the combination of the new shim and the shim that be create by the vue cli template |
vuejscore | bind the v for element with ref cause the movement animation to disappear when the list element be remove | Bug | vue version 3 2 47 link to minimal reproduction enp9ve1v00aq sudl0loyjdnjvbiubexbiauhdahx1knpvautbsorajikv9ffekaqavakeipicgicqaqdai hjhp wwzdpkmqcql2tf7zt7o2 e2twtboddcohw1krc5g0gqribbvzo6fsc4hczw4kalhm58sce1zvkt2owkcb6oqvntp1m3iocxumo4v72qypjuixjcwiursfgc8z0xf5keu kslgshca 5tkht6tikvrwazkdtpbbt9yblhuqpqlfpx7xm5pddmkrgxgcnknyl8em8uyzcy wpknhoppnwfdpfduirlygxz2axgxls7yy4cdzxrgxfzei 0tcmum58n1ajsu4k5fmckqf1 fcnqbn3lq i4xbbjptxwreji0ygykwskviozipa7cczjeeeukqeumkdszbkl5dnda0xtxgl4jyxiphkjkwkq3klclfzkqtxfgzge5yqmfphk6yg1pijaseqektsqigouo1j0ricaoqcxnfdnrvnji1adngzri6iipd0i6damrqaadzvsiugjfhce9pxnckzpyky4woqckyt1swelgnrmo0rwxg8nq6hkkuewhoxia9dtlm3eppi gh9cnazvh42 lanfw2t6sqgnblnjgfejue5c dqkugrq0fgwwqut09qbmvzyf6 libyglyjjypwxtjv3yqe7eyvnw8 96lf7eg7x8on uf7beomiaz6ugzeczxiqrzytitxizcpcin9vcs mcxv4 ncflcsmtpaqydhp9s ej rpen8gm51jz9 g37pnbz9fk0f9 g frgepoh twc 18yx1e7v9p0ed7zuyhw3vhxc7w 4mzkqbxweb 1ggf8nxvctiv 2hu32cdypge58qgnmhhfmeux9fkzbvkicm51ubfl8wio9qnindfw gbbwtwiqgt4 cplaxmhbfwwhpsfztbeybs7hn8jbk1ye5kvoxcvqcvngjb0fi6bhohj rcpzaei6kpoaet4obggzgxxcc3zon l9im9wzgjn750svjvrq0lr an24fr0 step to reproduce create loop element and use the ref bind to animate the transition group list remove the first or any of the last element element from the list ref transition group what be expect the element move up what be actually happen you ll see element overlap system info no response any additional comment the late and alpha version have be test in sfc playground and both have this issue sfc playground alpha |
vuejscore | template compilation fail when use v once inside template with v if | Bug | vue version 3 2 47 link to minimal reproduction dev enp9jk0kwkamrq9ssnzmqawhvnf7zezt1krzqyatc ndtusptykrkpclexndiubd1ag5fiwupo mo ulsmqkznkis0zvl60fphot9jmkmizb8gfcmsyuzlhnptcgpigwgmrfqkzcmep7cl4 ehebdgishtzrscfkxa63cgooktem9vfx1efgzf4yq7xnyqeqg9uv9fkvn jmpouak1mncq ejeyli8lxi7bbuos rel6k5vnfgln2y 0c7bwt9b aklkgju step to reproduce just open devtool console what be expect template be successfully compile and render what be actually happen template compilation fail js typeerror can not read property of undefined read 2 system info no response any additional comment no response |
vuejscore | watch do not work after build for production use npm run build | Bug | vue version 3 2 45 link to minimal reproduction will add zip file to this issue step to reproduce 1 run npm run dev 2 observe that watch be call 3 run npm run build and serve use npx http server dist 5 observe that watch be not call what be expect watch callback get call what be actually happen watch callback do not get call system info no response any additional comment create this issue to bring attention back to look like the bug affect both watch and watcheffect |
vuejscore | inconsistent behaviour of whitespace condense handling if second element text be an interpolated var | Bug | vue version 3 2 45 link to minimal reproduction enqduktu20amvqo7xagfbi0dneaqkaa6dnbv19qmzmoaw pbckqsbn2lz8njwpecrpkgqlir ejqvtckr hh 3zoursipczoh4ew9v5qww28cxfgcnjcbg1wbjjuzspb2czzimdoblep io7g6md6yj0akagrxrcaa5oqbeg7rftxomgamxutwgalaefgwpa1rf8lv2sbckxb6zniklxfxwreudz7q 3ny44exeqst5tembmyira9agu3dq3ezzrozudbl2yh7 qxkvbegmscy nq8x6qo dfd3nujcy4o4f fmq5re8 fc 4tc1x hhf9rpnh0oadbn6gbyqsnoekg3lehi9friedkx6 u8cuby9s uvlit9ujy99xu5vscc9nwy7a rne7 dx1 qysh3 yykcbxqmyvjsrnyqnwa5sa5tpz qsn a4 3kqucukmdmpx6ijp9uitkmhe6bchvpyliferm0wrzlborh7wsdeldisopjlyccwzvth9hy 4nzv oy30fjwjze9avxcgty step to reproduce n a what be expect as describe by evan s word issuecomment 450012518 indent the subsequent element will add a space between text content of the two node vue when the second element s content be a variable not hardcode text the template compiler do not recognize it as text and remove the space vue what be actually happen it output foo bar in the first example as expect and foobar in the second which be not expect system info shell n a it s vue s sfc playground env which use whitespace condense default the only requirement to reproduce any additional comment the behaviour be inconsistent and it s especially problematic when you re deal with dynamic content a classic real world scenario be loop through a key value object and output a definition list of thing for example know workaround set compiler whitespace preserve would work but be not an option for I because it break a lot of other rather critical stuff issuecomment 1381701932 manually add html entity but damn this whole condense thing be not align with the last 20 year of html that I can remember of and I would rather not go down that rabbit hole |
vuejscore | templateref overwrite reactive datum | Bug | vue version 3 2 45 link to minimal reproduction dev enp9ustu4zam bvcwcapuevapi6gw2spe96rlonnnnpaj5uon4xhfy8lb23aavwjj9emofqsfocgp4yifv3qowkecsmhe 2mdt4szbbx35ozeby4rm9hw indtr13iwco48w7l5r25lbrhimfjbn85mry412nvrpmzgtqhvgpsfnaf1lihi806kewsau5ym1jepecv15bpx1kezdfyhilz9js xsns5kgqmxfsdxwlwbtejpabm0zquqkv0a1rssxgiu6k9uidhzwbh6p rypkrex0tz iahzxk3z ype3nyerzggfc8mol4gxgydii6lptsblmla3zirn7brh9n 8hy39iwjktgxp8ze 2tzmxvwh01qvpriybp1kux4lasb2zspsh yts mz gds6npeultvjqfnosa3eicqlvkrvw cb7b9woeypmr8zim3i7 yg y5 1md7xncljtscon9kgflri9srcsxfcwmt0q0ymx4p9gh7tvbd75no0vz4nxplc5tj sc step to reproduce enter content in input vue what be expect name ref non ref datum should not be contaminate what be actually happen after mount the active datum be overwrite by the template ref with the same name system info shell system os macos 11 4 cpu 8 arm64 apple m1 memory 69 42 mb 8 00 gb shell 3 2 57 bin bash binary node 16 18 0 nvm version node v16 18 0 bin node yarn 1 22 17 nvm version node v14 18 1 bin yarn npm 8 19 2 nvm version node v16 18 0 bin npm browser chrome 108 0 5359 124 safari 14 1 1 npmpackage vue 3 2 45 3 2 45 any additional comment this pr fix it 7522 |
vuejscore | directive method getssrprop have no access to expose property on the instance | Bug | vue version v3 2 45 link to minimal reproduction ssr enqvuk1p4zaq ssjx5pkjvoxu5duqfhposih4ohlm0ylibet2wmgkp dsdumiqgkcojm 43fm479m4a3dbivy11hpfhg0ddmlzssjbyeoihxjxvevxrtehrywv3djhpmqgk1tiydydtkw6snwv 2govlcgn9 k9qexyaonhkddza8emfgrvaoq nwwd0 r 0whjzilxcmoflnsrdqg9dcgxrdt8e f39xyb0yvaquqr9 jyfofrxycu9t2aj4tkcjuvceuxgfcgn 4e9t2ms8wlvedcaj5ueny7o4x5o6il6sre40xzvdkn8gtuavybw6rk xnju96of 2dqr5 hhq7edpg6nvicupwcggchsnznu1fhhdmvz2ntqo3hkf9eyhbanfcxpkswpuczpagmz4ygtmchu0rrjefptiu6vph0cuw4wqztbamzc75gj94bt8qyrpnnps90nv1rlrnei6wxlxv99ytf8n9 cnp5czyjq9ot1s8olsekdpqqds8o2kjnldilw7tfgk1qpwbocp9at2qw h0nnyvo step to reproduce 1 open the browser dev tool 2 search console entry with label getssrprop and beforemount what be expect the value 2000 should appear in the getssrprop entry equal to the console entry beforemount what be actually happen property exposedproperty be not include in bind instance in ssr but it be in the bind instance of the beforemount system info shell system os macos 13 1 cpu 8 x64 intel r core tm i7 1068ng7 cpu 2 30ghz memory 1 19 gb 32 00 gb shell 5 8 1 bin zsh binarie node 16 15 1 nvm version node v16 15 1 bin node yarn 1 22 19 nvm version node v16 15 1 bin yarn npm 8 11 0 nvm version node v16 15 1 bin npm browser chrome 108 0 5359 124 safari 16 2 any additional comment |
vuejscore | suspense issue withasynccontext call without active current instance | Bug | vue version 3 2 45 link to minimal reproduction ssr enp1vetv00aq isjc0gkydqtwlkmwwkhcsqlgnlchnb2on3u3jw760rrmv orf95tvekz2vn c1svc9vxzy1eqexmvslyojbw1e3srrlpbsfr6qsineqhbhzhepmr7gmzaqksvavfi3awa38isxabkqwwvkepeif73mjictepdgs6nid7wrnfuwgf9ry3uxbz8tebaq u9x1tjo38e7rmkfngwawjexfwez mz4ltozfkuwsegcqwz4uccl5ndexj6qucv7ozlhxgditrgxrjghov9gv2lqotevnuocedvhgxyy5rwsxvleysy2a1i2nudiuts0bhow7rs0in3e9qjjinkhlbimj l3okb9x2qup5lwoep4 7z1yeg0zt3zaohuz q g6gcruc7b6jsut9zwjvt91wrf5pov6a1mqsr9lvqvgiu8 bgkl7npeifxyeu1xzsyzc6dnljorsj3qdrud6d4ro3vy2emhuu3fze3quctdmrb r7vbzxhec6rfzk0bsb bsheu ktveflm3gt5qclr9jckelbsxhmbjpgqtmloze4ge2b43fnmnnqlmnhmnjznyima2lfiqxnou20whka84k8nevq fbjueq91sgz1g7ib s8mj3x69zspmyplh5v3wyftcuh4rr6 w222wvqcftstg8ergprjb9 3r0o5opxbzbd5jm7do4awmtllxroahyg2t3 q6 q7wbsqbbtvozc7h8gmj6beu26r6rd09ey9qew4hjoxbhpd8ewu3vave7s0boliq ogzdwglxbr4qosoukjtapzigpnydgf7xqsnfo6pqkoogcfw4wdxa d90k9 mzulmf0aiz4ysulehcauushcfxa0c5prk4vg07wxdun1hekkxhdam5zfrjuvdweqtbgtw1 fyjddft2 4hxstlna step to reproduce wrap a suspense tag around a component with a top level await what be expect the suspense will render the fallback element and render the default element once its promise be resolve what be actually happen neither the parent nor the child component be render I receive an error withasynccontext call without active current instance this be likely a bug system info shell system os window 10 10 0 22621 cpu 8 x64 intel r core tm i7 10510u cpu 1 80ghz memory 5 37 gb 15 71 gb binary node 18 7 0 c program file nodejs node exe yarn 3 3 0 c program file nodejs yarn cmd npm 8 19 1 c program file nodejs npm cmd browser edge spartan 44 22621 819 0 chromium 108 0 1462 54 internet explorer 11 0 22621 1 npmpackage vue 3 2 45 3 2 45 any additional comment json vue 3 2 45 typescript 4 9 3 vite 4 0 0 vue router 4 1 6 vue tsc 1 0 11 |
vuejscore | kebab case boolean prop be cast to string when use in custom element | Bug | vue version 3 2 45 link to minimal reproduction step to reproduce create a sfc component with a camelcase boolean prop use it in your app pass the prop kebab case prop be well receive but cast to string if you pass the prop camelcase it work fine what be expect a boolean prop in the component what be actually happen a string prop in the component system info no response any additional comment no response |
vuejscore | v bind style not work in some edge case teleport transition slot | Bug | vue version 3 2 45 link to minimal reproduction enqdvm1uozaqfpvzx9jkae7znno97hx3sl1u4kjgkrgf2xopsaso796xoyq2kfv7qcx4vp 5kdmq386l xbvqi0zg1cxjkvcaczxlbm18kusdfl0lyu s4f7ntzbuimfq5gr1b3dbmseduuy62a9bwwr ahv7fr6d2vdec ejm8s8nahmbaycum1a2vmscqanswoueyaz5bzzi e4iv9ojdj24muwmof u v57pzbww2yfxhktsytvtqnbkvjb6mvg 44vranz52nqm3dsqw5bforliqgv 7smq3c8smvscikxs ofj3i2o7hcn5a4vgykcnc8aygiagl3gqrnkeakow0ndrz6oujjufls pk0y dirzoobqkhixbu4aqbsg3m5eroonrpjwcobw1jbp7m3mwiq9nt28n4xoztphzvfwbvtqfx5jc6ykchltgg6ki5knzw2lq3sqq4u4tgctvxnbmkkvz66k2r30te5v2bz9wiyws9mr3qxo2ynv9kmd u4efy6fnl20zeumon6wzt9e2yjnvwsekcq mii5pmhikhnbwsfiurnb9gl3gdrwx0uqdxm5cifq step to reproduce click the toggle button off and on what be expect all text should be red what be actually happen use v bind inside of a teleport inside of a transition fail it do actually work if there be an extra div wrapper around the transition however in a case where a v if transition be be trigger because the parent component have be unmounte this will not work system info no response any additional comment see and for anyone encounter this bug in the meantime a workaround be to inject your own css var with vueuse head in my case there be only one of the component at a time but you could easily generate a unique name usehead compute style child root my special css var myvar |
vuejscore | vue ssr hydration error functional component | Bug | vue version 3 2 25 link to minimal reproduction step to reproduce in ssr mode create functional component return tag with text node and expression inside e g text node expression what be expect no error warning what be actually happen hydration error log vue warn hydration text mismatch client text node expression server text node at at vue warn hydration child mismatch in server render element contain few child node than client vdom at at hydration complete but contain mismatch system info no response any additional comment no response |
vuejscore | activate hook be not trigger when mount child of an async component | Bug | vue version 3 2 45 link to minimal reproduction enrvvmfymzaq zuddok9mrcnnxd76sm943vigcdavgwsiwmadso d4vaycfjsxpql4jv7nusnvap8bzlgdqveisvuqlkpqafuio3mqdgrsmkhkdrllcxoodbidsbadxocnajrk5diq0vi5om94zjvv3mqserniowevellkjky9b2damwfvxp va1ctbwbcyb8bhxbdzfb2bhfexhifgjvmazsc ni6 c7bnmc4n7 m6 445yrjuhjc uu3s zupkx0n54vbed8q nukjzugd5bu d irozrye9dwd0wwgxu4uxgx748ajm9mpqtanfkryjef9nfftinu7miehfay6zop0fiueakxu tounxsu81qmsjgkmqjbad9reiplm8uid0khbij4rhufblmwh82j6sfucflgfem36bpwna2vppgs0 ipz krlyrxzoaesum1rf3pmrsbalqvvik8iijeqm0pv3 shownojbqerahq1rajmffxo1qfandzpckhtieavptrjfjgxwqgqn0ztdxvueir0vddnmjtryxlf31lpuqzbu 9sy4lufqh5c gtkxturmebv c9s fioitj2 nbtoekarfh6pgigeuu1zovsd7ygto15s0czfhzn i3grhomuy8nojupnqsl84vzzitbgq2xpwf0hbledgdljnimcngy3y5d6b6dzjitfa828ldubaedxde1tb9y24krxtku6idndz2 ylffruoj8xe00buh719rcfiuf0phhqqd7ojehvk ksv9dlqqee1ocwo7oeg58k7f 6m33z1 stkh3f90z shxaahza step to reproduce enter the playground use the button to navigate between async component what be expect child vue be a child component of parent vue would trigger onactivate hook when mount follow the doc lifecycle of cache instance what be actually happen child component start trigger onactivate after the initial mount system info no response any additional comment no response |
vuejscore | bug when slot be use with v if the slot content be not display as expect | Bug | vue version 3 2 45 link to minimal reproduction enqfks9ugzamxl fy6wdvmgd0w5tpz33afwogjo2jfes6ahx7noaufb bhbsn n9ts9ejim7flnculdyytw49k05zeo0rlsppvisyidk6gy2vlpzjo5a vwotpnhzjdmyfjhpgqthdhp gb7qnpwuxt4mkmut noeguegynzjxqbpkfwe63guzciuo4znrc hg gxhoar taiktq9xn gmzmpnvpppsvk1atfwchs4ukogta5tnsdnbfoprhlwma3qzurinlqbevn ipp45pyf02xslftladm5ykmtzef6cv2dyp8 ydl7eexkzikwchztjze mszl1vbcmvlta25vqx21z50wcmrolovt8cwx0hym7f4jts0eyks0sl9i ml9jv3ialwwes8mm3q cic1wtauhl8nagxipkytnj0klfmpu4u uwelritmthobd9p n4kqo z w9efcres1l kuf9ff1zxz1psa3gfe5as4 step to reproduce 1 open the reproduction link 2 click the toggle button 3 observe whether the slot content be toggle what be expect 1 the provide content should be display when show be true 2 the fallback content should be display when show be false what be actually happen the slot content be not toggle system info no response any additional comment no response |
vuejscore | ssr problem with empty text node in render function | Bug | vue version 3 2 45 link to minimal reproduction ssr enp9udtqwzam rxnl04gtd5dwxj7jhmmnfxwtpef2ekkjf8 oze226bgbf2ozphkq3h1lj 3keqx9jw1lmyvabwzfoakhwwigxigiatbmk4qowxexvwem6rvgkcmgmfqu qz4yrf2ebhskceqg2ndxdwemat rip00gtc8rlzcbjybnd8lfo idhbk560owrrlcpqxgzvvx1qdypogq bnqemqteap21uoxbnqbdxnisqa0yjt7jecy 0eshsju0q9ufbymy4gpx3zwxw2fihptfle6cvnrw8mbhhtxc8irus6jkmgrjb4shxccl4vcn3x8l6pplx0vboxum9bqznhr1y7st0diyixmiuaogonnpbwh2smhpep8a 3hu8wlhh weawk step to reproduce click the button in the playground example above note the console error the ui also do not update to show the new text what be expect no error what be actually happen uncaught in promise typeerror can not set property of null set nodevalue at settext runtime dom esm browser js 9332 24 at processtext runtime dom esm browser js 6536 17 at patch runtime dom esm browser js 6491 17 at patchkeyedchildren runtime dom esm browser js 7274 17 at patchchildren runtime dom esm browser js 7217 21 at patchelement runtime dom esm browser js 6731 13 at processelement runtime dom esm browser js 6592 13 at patch runtime dom esm browser js 6509 21 at patchkeyedchildren runtime dom esm browser js 7274 17 at patchchildren runtime dom esm browser js 7217 21 any additional comment if you turn off ssr mode in the playground then everything work fine the text node must be empty initially to hit the problem any other content seem to be enough to make it work I d imagine there s a problem with the hydration process and the text node not be create for the empty string however there isn t a hydration warn it only fail when try to change the text I wasn t able to reproduce the problem use a template both text and v text text seem to work fine while h p text value fail similar attempt such as h p text value and h p text value h span work fine |
vuejscore | onserverprefetch produce an invalid warning on ssr | Bug | vue version 3 link to minimal reproduction ssr enp9uktuwyaqvqpiuyildtpl6ktqaspfapdsqdnohnmabuyosrh7b3bsjzw6aobzemzmy jv1hbjahzdk1djaz1z4afloqwpw8m9k3wnnwntbw16nkubovng0 h3m2gph9n7abwb95qgx58ogfidpmdp9mdta8tevrvtpdsor9g2uolgdq4wkf iizt71jutc7bd5bev9y0rtw6i4i4zi mdaqbhwvyziwscm90i90awo 1sezcdfw8km1o6jtwospjnhcv7wa9vgzarjymfevcx1d6kffdibloyvtfeuintiofejxvvzgvo3ur46g2npktpv6fn3ttloyvqlerg a3dlzwltoqvlc7oabi0dspnbom4ufynoqksfclp3lu3kuvx1pebnf1h8fisvsaps8mpwpwrlzqxb0jekietz46sgqtwckefaah 43ya ufnk6avw8mpr dwkq step to reproduce 1 in setup define const datum ref false 2 in the onserverprefetch life lifecycle set the datum value true 3 get the datum in the template be false what be expect datum value be true what be actually happen datum value be false system info no response any additional comment onserverprefetch no response |
vuejscore | vue compat parent be miss when functional component be render inside functional component | Bug | vue version 3 2 41 link to minimal reproduction step to reproduce run provide example what be expect direct ok nest ok render ctx parent be available for both descendant what be actually happen direct ok nest null parent render ctx parent be null when functional component be render by other functional component system info no response any additional comment no response |
vuejscore | maxiumum call stack happen on hmr with ref setelement and edit that component | Bug | vue version 3 2 41 link to minimal reproduction step to reproduce 1 open reproduction 2 change const count ref 5 in foo vue to const count ref 56 3 the warning happen this do not happen if be use instead of in app vue what be expect no warning happen what be actually happen the follow error happen vue js v f54006de 1274 vue warn maximum recursive update exceed in component this mean you have a reactive effect that be mutate its own dependency and thus recursively trigger itself possible source include component template render function update hook or watcher source function system info no response any additional comment original issue |
vuejscore | werid render when use compute and h function | Bug | vue version 3 2 33 link to minimal reproduction step to reproduce use above link use case 2 what be expect just msg turn to 2 other element do not rerender what be actually happen arrow be rerender and also disappear system info no response any additional comment no response |
vuejscore | fix 6859 patchprop for image prior prop load | Bug | fix 6859 support image native prop load |
vuejscore | render function be not patch when use vue compat and extend | Bug | vue version 3 2 40 link to minimal reproduction step to reproduce it will raise exception immediately what be expect foo text be render what be actually happen exception be raise uncaught typeerror h be not a function system info no response any additional comment the error be due to vue try to patch render function in extendedcomponent type however it be not there and will appear later when extend will be apply |
vuejscore | image inside root component be request erroneously | Bug | vue version link to minimal reproduction step to reproduce add the markup for a root component to your html document and put an image tag inside then create a vue app and mount it to the dom const createapp vue const app vue createapp datum return const rootcomponent app mount app what be expect image with the loading attribute set to lazy aren t load by the browser when they re invisble style be set to display none so no request should be make by the browser for the image what be actually happen as soon as the rootcomponent be create the browser request the image url just remove the javascript line mount the app to see that normally no image be request system info no response any additional comment the image be request as soon as vue add the src attribute to the img element when create the dom happen in line 9579 try el key value image immediatly start load although loading attribute get attach to the img element later on the image url get request immediatly after this line have run interestingly I couldn t reproduce this behaviour create an image element in javascript and set the src myself const image document createelement img image src img do not load here image loading lazy although that seem to I to be pretty much the same to what vue do here a workaround be use the v bind directive for the image src then the image do not get load as expect |
vuejscore | static slot content vnode s el property remain null after the component be mount | Bug | vue version 3 2 40 link to minimal reproduction enqnuktu2zaqvcqug8markaflssbkzoc3qrdteaxzreqnhbu8besshmiukjokjvlciepr0gciaggqhjz3rxhcmygx4yhux7jklsusz3x4nd3zs1vj422hgawucmgd htao9ghi3verlqlh2evv 1naecsgiiaeqbukryzb1ma aojag9bgrqre26artdggd7k0zfhcowmso5bkhf5mzskcm6llwh 51w4qpdyjsqjpmlpeqshenezmmf98ytgeuvudzsrkt2gjhme u7iwwr5elh of ognrzj tu3sy gf13qenizwut8xzko7qlhzvixbtq2fh2mebr9yl0jg5cjwgb3h85zcprwctznw4ebyfklz2v7rm8niixdvaoq sbwev psowqh4be2on2xlq5tnvqulcvqjsgf6tkpr92naibfwgo9zyoxel93fj7b3amqtbvakvq2z85wu fcqzsgsx n8e2groxv726zykqm7atjf39o liu0wlcvl5yf xw5cun44vcyhvo2v6d7ts6hbfippaczjrmsksyfo9x8lxax5thf4 step to reproduce see the vue sfc playground link what be expect switch vue version to 3 2 39 the output be the dom element which be correcta image what be actually happen switch vue version to 3 2 40 the output be null which be wrong image system info no response any additional comment no response |
vuejscore | component be accessible by this from function declare in | Bug | vue version 3 2 40 link to minimal reproduction dev enqnkc9uwjamxl fyguqnehbtqhm7d1ykwkkgc0fjq7tvpxd57qcgentbrh92 t 7y8a qudxrnmo1ulfexcsxhzeptm2 igwqnqdjnbfb2fb0ov00inveoly2shsi2k5xzv8l51c4x103i9xmeghphlj95r3 rtes0l8aip5kf0tzirxkebtq9 gpgigbs0vvn ktjdmnbgvbmpt5zgriyhfqvntjisdg qnuhr1aazx1dbvabimw23bcazf3phfadmpnmtndpl29momwtcq9krf3qfsw2yhk9se pm8i48np stkctbzq6vhdlbysnoichthmguxe7klruhqolivgn11xp7eouv g1l1it3ea6try7rfyudisjz5m64oorvxypq1 qo45 wj 0d8kn2c1qy9lmjg38aeufsra step to reproduce 1 open reproduction 1 click output count button note that click foo be use foo it work well when this be click foo what be expect can not read property of undefined reading count error happen on dev too it happen on prod what be actually happen 0 will be show in console on dev system info no response any additional comment original issue |
vuejscore | suspend component still trigger watcher while be switch out | Bug | vue version late link to minimal reproduction enq1vmgomzaq zwrl2qlaneublt uhwvxfgywkmxlduqvhh 3sf2gtioaaxvkoram2 ex2 eubaxrbnprfawg60n1w4sule lxkad1ozbxewfsweon hngvt1mqbhblaowziqdhzgb9vbqv7 sxrmm yw2jz6r78yu rphbh9ho1ktabuandok762d3inxzc7g6xegishhjkasz dps140qcu10ncpcelyumazznlrgx s3qefwf6sum6wkvwojmuh7yocmpsauhgxavq6 n4w10jjb wgte ziwlhrrmp f2jrh5ghqswjzmwg5vi5wo7sb0edqrwjkagikbonun18yyk8l armkp pikusjge vdo7wsxjbf6omizsyyqrqcwjyszrkvxoavvkuw39he42u6bl6s0zo3r8waztsh8z6mzrehhj0hvhtsejzz5ka9cgect5dnrhgywf6shbkz2087lydz8clyes3dbgwwhkyczut0sckfjbc1u1xhaj99lwjohp6jkp8hvsyf h57wbugihkopms7qvziehncvcgwhor2a dnhwmlwbzhbvilzith0bivbw as1u9kjdzz8iszyns54lqs2fnl3hw c q k4elhtw9ssk1gqqxrvzw rx5et7syhflmff2 hxa4dgmobyphqhzclv7xjy anfpe2b jp 8gnyvngq step to reproduce click the button what be expect only one watcher should trigger what be actually happen both the watcher of the leaving and enter component be benig trigger system info no response any additional comment in this scenario the update of the variable be watch be what trigger the switch be this just a race condition since the old component still need to display I would say it s normal for it to render due to watcher this would require vue router to have a special handling of the current route so |
vuejscore | fix ssr don t render v if comment in transitiongroup | Bug | fix 6715 |
vuejscore | watch callback have something side effect when call createapp in the callback | Bug | vue version 3 2 39 link to minimal reproduction sfc playground enq1u82omzaqfpurf4hebcv7ajajstruodf2whpgyvjogmzza6sk8e4dy5jn06q3vssa72e st2m0ymxyugx2kv7v9jgedik3hyzrmmntgqjwkxsemupqfmoloaebeqhhgkqq1ui2r9nxdyvunmezu45hlwr f5jdx gg dqudpgqlw5cujzm49vhquxm6zgcisrgvjikbvd4cu3cxsdxguzxcne35os4wk2x6u54wxjlm2llvowoxlb 6tqv8ebtnxetlpnkleaxuzpuvwlwibd vg3qjxlpveplc7lz hav3p7kxbdrnoupnd1slndg5sglxixviiufvgof4edj0v2jxp7tyejyxtzsytegelptxx6pdmxva wuvobb5ak72o5wjkfkw rf1yf3hwvw77xpnfb2brfl qr2tcbobwqkv4pwxs1n2r7zkljo2fgc 1lvvn02 k o6 oeku7gmewhtmemcvklnnls06urmhb121uxe no 4eehdwl4tlim7key xjvs6i2oi43zs9p15frgfbuwjowl5hzow16vut3dik 4 ybjxdi0ldo362eo3h5yts4hv8njcmjigxvtenrro xt2o 0j8ib7k9rn8gtm0fqbe2nfrq step to reproduce 1 open the demo enq1u82omzaqfpurf4hebcv7ajajstruodf2whpgyvjogmzza6sk8e4dy5jn06q3vssa72e st2m0ymxyugx2kv7v9jgedik3hyzrmmntgqjwkxsemupqfmoloaebeqhhgkqq1ui2r9nxdyvunmezu45hlwr f5jdx gg dqudpgqlw5cujzm49vhquxm6zgcisrgvjikbvd4cu3cxsdxguzxcne35os4wk2x6u54wxjlm2llvowoxlb 6tqv8ebtnxetlpnkleaxuzpuvwlwibd vg3qjxlpveplc7lz hav3p7kxbdrnoupnd1slndg5sglxixviiufvgof4edj0v2jxp7tyejyxtzsytegelptxx6pdmxva wuvobb5ak72o5wjkfkw rf1yf3hwvw77xpnfb2brfl qr2tcbobwqkv4pwxs1n2r7zkljo2fgc 1lvvn02 k o6 oeku7gmewhtmemcvklnnls06urmhb121uxe no 4eehdwl4tlim7key xjvs6i2oi43zs9p15frgfbuwjowl5hzow16vut3dik 4 ybjxdi0ldo362eo3h5yts4hv8njcmjigxvtenrro xt2o 0j8ib7k9rn8gtm0fqbe2nfrq vue3 2 39 2 after click it log 1 1 2 2 will appear cleanshot 2022 09 23 at 18 01 40 what be expect 1 open the demo enq1u82omzaqfpurf4hebcv7qjrnoqy2e i1pzyewbgwugzb9scqqrx7x5hk07tqbs j5vuzb2wpy rgjbh6jhbr3hw2mqqoqtfhrgtaoy3bcbarfn5ykuoucos5iztsqggcyuowyvbhwzd1he4cqzltdgfvsr7 wn2f4cy9fnqmufbvrhx69sxjvwfbzcyrobxhziyueutgmhjjtqjdj3hzdhek8bemrhiazffqbjjbmgvbqyu xy5e8d8p9fxwbi23f63ugwqsqbftsy5 crzgvz7wjsrpkul9aqxz8nm48nxc grekkseheldnwxw9yalaaveprukpv886sxh4mmsfepc tpj6dlf cyjd4b48y2hhulmdo dzdru4igl4rtadrdkz tb p vbzffy7bvvglcelzg8qv5ivb1bk6faorxqxzd7q3zhrpo ogz ej7ww8w xb z grul7rdsyxroe0acwkouv28pitpvfy8hwbg ht6y4 ar6c9qvhsogbecrjvoo zqkaylidlh1nxl9eovt5yk5axqgmxxwp29od2iq7t7jshf3jal27frb6zahlxczig7w0lwwoanewlw0t2v g3wj clzh gr1mfwcuzt9bnm9x0e vue3 2 37 2 after click it log 1 2 1 2 will appear cleanshot 2022 09 23 at 18 04 21 what be actually happen log 1 1 2 2 system info no response any additional comment no response |
vuejscore | v memo doesn t work with v if | Bug | vue version 3 2 38 link to minimal reproduction enp9uetuwjaqvcrug4ogcvu2fq0rpufdrtatkoi sp2wihl3jpmu0vrin n 4ymyx wpm2dbmsyl11ta3gmjc2frpu1lkahdkvooxrgwykki3ehhzzge9jw5gq7qhgorshlly9no8o0efmsienjouusckjspqhiccdzttdqjnw5eywgckziotkep4ekl8hyrhvgvqcomuqwea9ncebdxl5qez781ps05usykvqjhzmzpmrhzrlvyf6tomwcbnlqyfjtylzm418svdj02xtnn tipjgwxratdezk6f8rc1afyp2w80bb8ymvrve97bijslphcjrqv0lf080bp9y 3pmpepucnll6dnqo2pounbpzoksc6im6da lzto hbpdv9ly2qvds 4hlezdqw step to reproduce 1 click the button count 2 click the button change show 3 click the button change show 4 click the button count what be expect 1 the count display in the will increase 2 the will remove 3 the will show 4 the count display in the will increase what be actually happen 1 the count display in the will increase 2 the will remove 3 the will show 4 the count display in the will not increase system info shell window 10 vue 3 2 38 any additional comment no response |
vuejscore | select with more than 4 explictly type option always return string value in v model | Bug | vue version 3 2 38 link to minimal reproduction sfc vuejs org enrvusfog0au jxnxtskqgw1myq29elvi8e9uhhyln23ebvqgmk xaqtjw1z2 szdavm5leplobdy3ivgauonp64cc3dqvmrs2sf70gqgzil tikwzrewpxxx9ckvogcv5uigizrnc3x9ampx8osyzjtushb22b3ao hmgcnfb40uuas2iwsrkzkiphlfpfoxfplzctmhnl1lobljmic7i5y152eem2clitwuw oxy yuuxdpdbv3fhfpx zlgsft9wnqzhy39ywgopjlonnamey wflrxfdrpgqadzjyts4xsdcianluu6 t gbq8m77iox2hnoyvsmsmb4dugt5nz769ikay19f40l1mmauyra42snuyl6vyjn8eihkwvnd eyni42hdshxbevnb2ycwdqgcicuwib9 7hsrpt0cet7tfrcjorgotwcww3lye step to reproduce I have a simple setup with 5 option and the value all set to number when there be 4 option the variable be set to a number type as expect when there be 5 or more option the variable be set to a string see the example link as a demo with two identical select other than the number of option if you instead define an array and use v for to create your option this bug do not appear and you can have 100 option and the value be always a number what be expect the v model variable should always be a number and the number of option set shouldn t matter what be actually happen as soon as more than 4 explicit option tag be present you get a string as the value system info no response any additional comment no response |
vuejscore | v model lazy be not update the value of an input when it have a focus | Bug | vue version after 3 2 0 beta 5 link to minimal reproduction step to reproduce 1 type jacob into the input 2 hit enter same as 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 system info no response any additional comment the value of the input be correctly be update when use v model without lazy modifier 3 2 0 beta 4 do not have this bug this bug occur since 3 2 0 beta 5 |
vuejscore | maximum recursive update exceed when access a responsive variable in onscopedispose | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce open the browser s console update any code in helloworld vue for example console log watch element console log test element observe the console log what be expect this component will be render only once what be actually happen vue warn maximum recursive update exceed in component this mean you have a reactive effect that be mutate its own dependency and thus recursively trigger itself possible source include component template render function update hook or watcher source function image system info no response any additional comment I also run some other test such as comment out line 11 of helloworld vue or use onunmounted instead of onscopedispose do not produce this warning |
vuejscore | when use non ascii alia for list item in v for directive event handling be not work as expect | Bug | vue version 3 2 37 link to minimal reproduction enqduktowzaqvcrgtanuxpusvhr2loaamiwbtovbxlfspwhfoqb3qoy5gfydct6lfaqirjhm a9yvrszky8lzgnwejsq4whh740u6gftwvtpcyzunkhe7gexfmpvzgywydassy4k5rewc2j0adhw5y69arquojztkwbyzeekitcizo0nijnds10wtuhyzxopoymkx7ja0gwatsyh0xyzhtmuqushkh2stlb2erlcrbrsratwrryohsnqjayb c twi210an89j7yn6abuju1etoioduxvutenr1wtvq ce8u c i5uwg9ruar58hc9r1eegr08pb4 pjochkv2fogkbhux0kindmoiogobanu w0up lddtnxdmjrqf26jtxk nsxfrucuujxjp47qpnl9mcj gsrhzch5rgdlrbf zwe pgnltlgu557elcrjhzss21vzng6pjobos7h5aabrvtyxakbtfgfvucldqfmd vfshttrtm9rt4lhea step to reproduce please press the respective button to confirm the content of the alert what be expect the alert will show the same content as the text on the button what be actually happen for the one use non ascii alia in v for the alert will only display the text of the first button system info no response any additional comment it work well in vue 2 7 8 |
vuejscore | set custom directive to empty string cause syntax error in generate code | Bug | vue version 3 2 37 link to minimal reproduction enp9klfuwzamrh f1eiwqc10nrwd3fohxbs4dp04serbpn3b0l xcooohblpekcnhxfzhmozrwha0 gy5ijakgvsxzh9pcswq8ijmkyjpfqarvxwyataap4vccr c wby0lwswk5p1uvlnt2jloqckefl0fqfub3fev3 bicc2dvhvooq4cthlcw8vv5tjjkvohjgwd6xan9mnhorp cnf172lyae6had7g5mqwtvbee zxymraoszlp0akduypebq3lasylunfd6wl11kq1yoyxqfb1v6jvxqrg yeisgvz5b9g9njt step to reproduce use a custom directive in your template with an empty string as the value e g or what be expect the custom directive handler be invoke I don t know what bind value should be probably some bottom value like or undefined or null what be actually happen when use client side template interpretation the custom directive handler be invoke with bind value undefined which be fine however when server side template compilation be use the js code that be generate for this template have a syntax error for v custom directive the generate code look like this note trail comma in array which be invalid withdirective createelementvnode span null null 512 need patch directive custom directive for v custom directive foo it look like this note double comma in array which be invalid withdirective createelementvnode span null null 512 need patch directive custom directive foo something similar happen in ssr mode v custom directive generate ssrrenderattrs ssrgetdirectiveprop ctx directive custom directive v custom directive foo generate ssrrenderattrs ssrgetdirectiveprop ctx directive custom directive foo this then result in the entire app crash because vue attempt to execute the generate code which fail with a syntax error system info shell system os linux 5 4 ubuntu 20 04 4 lts focal fossa cpu 8 x64 intel r core tm i7 8650u cpu 1 90ghz memory 189 98 mb 15 39 gb container yes shell 5 0 17 bin bash binary node 16 9 1 nvm version node v16 9 1 bin node yarn 1 22 11 nvm version node v16 9 1 bin yarn npm 8 5 3 nvm version node v16 9 1 bin npm browser chrome 103 0 5060 114 chromium 102 0 5005 115 firefox 102 0 npmpackage vue 3 2 37 3 2 37 any additional comment no response |
vuejscore | vue drop value from | Bug | vue version 3 2 37 link to minimal reproduction sfc playground enp9ke1oxdamha9izt1tjjaljmqd2bewny4pgevptlnao96dpgexammy8rp9pux5qp5t6temalajz2stakpkddtbhfg3vhocprljscia8zrfyob1chmfjdlq iiso279tmp9akzzpobjsdur3btwkszfrpbn 7oz3 bazhkzobtwgif0brydpcnciohrhg3 4g5vb2v9iisdn1j 4rhknuihml8dnmqorcjpqbk4aqm rbipwvp7xk9w4t7sokvvuw5ipfbivjtr gskajbqcmpqpbkidythjir0j ln9r 3ykuitw0 fwqovg step to reproduce visit testcase what be expect both button should have a green outline apply on button value what be actually happen the button inside the vue app do not have a value attribute after vue render system info no response any additional comment this seem too basic to have go undetecte so sorry if I m miss something obvious |
vuejscore | content for literal | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce visit testcase what be expect both custom element should render identically what be actually happen the custom element inside the vue app render an empty iframe because the |
vuejscore | hoist element attribute not be update on re render from a fail hydration | Bug | vue version 3 2 37 link to minimal reproduction ssr enp9jz1uwzamha8iaiknxnjqiiphgugbonxv4lq0o8d6auw7g6g7v4o7ba2qjxzk x65848qxlycb3lhymmyeptkmdzps x7bnrknsy1cp182mhthneeyhfodxepscejsr1hsmxcb9kpo09lnhoxirnn3tnnqfebg9pevrug 0vo3fy9xworfznc1vxqvgiol19alh6ujk7lcudoz8 8sgvsemqtepc 2ith q2i4i27k0xld5re8strik2ucrrl37copm4yvwjxr8acggibb q etcdft8 mgqwn8agwwlawffmf6tp3ijnyiwefghbr4cq step to reproduce run the example with srr on and see that the console spit out a different I d than be render it even give you an error message tell you that there be a missmatch what be expect I would expect it to hydrate properly what be actually happen the const i d be never change in the template system info shell system os window 10 10 0 19044 cpu 8 x64 intel r core tm i7 4702mq cpu 2 20ghz memory 5 95 gb 15 88 gb binary node 17 1 0 d programme nodejs node exe yarn 1 22 15 c program file x86 yarn bin yarn cmd npm 8 13 2 d programme nodejs npm cmd browser chrome 103 0 5060 114 edge spartan 44 19041 1266 0 chromium 103 0 1264 49 internet explorer 11 0 19041 1566 any additional comment I run into this bug because I create a unique i d in my component setup that be never go to change for the life of the component that s why I define it as const an not as a ref then I use the component in vitepress and it stop work when I use a ref instead of direct assignment it work as expect |
vuejscore | ref in v for do not trigger watcheffect inside definecomponent | Bug | vue version 3 2 37 link to minimal reproduction eyjbchaudnvlijoiphnjcmlwdd5cbmltcg9ydcb7ihjlziwgd2f0y2hfzmzly3qsihdhdgnolcb1bnjlziwgzgvmaw5lq29tcg9uzw50ih0gznjvbsandnvlj1xuzxhwb3j0igrlzmf1bhqgzgvmaw5lq29tcg9uzw50khtcbiagc2v0dxaoksb7xg4gicagy29uc3qgy291bnqgpsbyzwyonsk7xg4gicagy29uc3qgaw5wdxrszwygpsbyzwyokttcbiagicbjb25zdcbvdxrwdxqgpsbyzwyojycpo1xuxg4gicagd2f0y2hfzmzly3qokckgpt4gb3v0chv0lnzhbhvlid0gaw5wdxrszwyudmfsdwuubwfwkgvspt4gzwwuaw5uzxjuzxh0kslcblx0xhryzxr1cm4ge2nvdw50lcbpbnb1dfjlziwgb3v0chv0fttcbiagfvxufsk7xg48l3njcmlwdd5cblxuphrlbxbsyxrlplxuica8aw5wdxqgdi1tb2rlbc5udw1izxi9xcjjb3vudfwiihr5cgu9xcjyyw5nzvwiig1pbj1cijfciibtyxg9xcixmfwiic8 xg4gidxkaxygdi1mb3i9xcjudw0gaw4gy291bnrciibyzwy9xcjpbnb1dfjlzlwiplxuicagiht7ig51bsb9fvxuica8l2rpdj5cbiage3tvdxrwdxr9fvxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuannciixcbiagicbcinz1zs9zzxj2zxitcmvuzgvyzxjcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvc2vydmvylxjlbmrlcmvylmvzbs1icm93c2vylmpzxcjcbiagfvxufsj9 step to reproduce break eyjbchaudnvlijoiphnjcmlwdd5cbmltcg9ydcb7ihjlziwgd2f0y2hfzmzly3qsihdhdgnolcb1bnjlziwgzgvmaw5lq29tcg9uzw50ih0gznjvbsandnvlj1xuzxhwb3j0igrlzmf1bhqgzgvmaw5lq29tcg9uzw50khtcbiagc2v0dxaoksb7xg4gicagy29uc3qgy291bnqgpsbyzwyonsk7xg4gicagy29uc3qgaw5wdxrszwygpsbyzwyokttcbiagicbjb25zdcbvdxrwdxqgpsbyzwyojycpo1xuxg4gicagd2f0y2hfzmzly3qokckgpt4gb3v0chv0lnzhbhvlid0gaw5wdxrszwyudmfsdwuubwfwkgvspt4gzwwuaw5uzxjuzxh0kslcblx0xhryzxr1cm4ge2nvdw50lcbpbnb1dfjlziwgb3v0chv0fttcbiagfvxufsk7xg48l3njcmlwdd5cblxuphrlbxbsyxrlplxuica8aw5wdxqgdi1tb2rlbc5udw1izxi9xcjjb3vudfwiihr5cgu9xcjyyw5nzvwiig1pbj1cijfciibtyxg9xcixmfwiic8 xg4gidxkaxygdi1mb3i9xcjudw0gaw4gy291bnrciibyzwy9xcjpbnb1dfjlzlwiplxuicagiht7ig51bsb9fvxuica8l2rpdj5cbiage3tvdxrwdxr9fvxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuannciixcbiagicbcinz1zs9zzxj2zxitcmvuzgvyzxjcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvc2vydmvylxjlbmrlcmvylmvzbs1icm93c2vylmpzxcjcbiagfvxufsj9 notice that this code be within definecomponent and within a setup function what be expect work eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgd2f0y2hfzmzly3qsihdhdgnolcb1bnjlzib9igzyb20gj3z1zsdcblxuy29uc3qgy291bnqgpsbyzwyonsk7xg5jb25zdcbpbnb1dfjlzia9ihjlzigpo1xuy29uc3qgb3v0chv0id0gcmvmkccnkttcblxud2f0y2hfzmzly3qokckgpt4gb3v0chv0lnzhbhvlid0gaw5wdxrszwyudmfsdwuubwfwkgvspt4gzwwuaw5uzxjuzxh0kslcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxpbnb1dcb2lw1vzgvslm51bwjlcj1cimnvdw50xcigdhlwzt1cinjhbmdlxcigbwlupvwimvwiig1hed1cijewxciglz5cbiagpgrpdib2lwzvcj1cim51bsbpbibjb3vudfwiihjlzj1cimluchv0umvmxci xg4gicage3sgbnvtih19xg4gidwvzgl2plxuicb7e291dhb1dh19xg48l3rlbxbsyxrlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wilfxuicagifwidnvll3nlcnzlci1yzw5kzxjlclwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy9zzxj2zxitcmvuzgvyzxiuzxntlwjyb3dzzxiuanncilxuicb9xg59in0 exact same code but within a |
vuejscore | root comment break the without any warning | Bug | vue version 3 2 37 link to minimal reproduction eyjbchaudnvlijoiphrlbxbsyxrlplxuica8ynv0dg9uiebjbgljaz1cimlzsg9tzsa9icfpc0hvbwvcij5cbiagicbub2dnbgvcbiagpc9idxr0b24 xg4gidx0cmfuc2l0aw9uig5hbwu9xcjmywrlxcigbw9kzt1cim91dc1pblwiplxuicagidxib21lihytawy9xcjpc0hvbwvcij48l0hvbwu xg4gicagpefib3v0ihytzwxzzt48l0fib3v0plxuica8l3ryyw5zaxrpb24 xg48l3rlbxbsyxrlplxuxg48c2nyaxb0ihnldhvwigxhbmc9xcj0c1wiplxuaw1wb3j0ihsgcmvmih0gznjvbsandnvlj1xuaw1wb3j0iehvbwugznjvbsanli9ib21llnz1zsdcbmltcg9ydcbbym91dcbmcm9ticcul0fib3v0lnz1zsdcblxuy29uc3qgaxnib21lid0gcmvmkhrydwupxg48l3njcmlwdd5cblxuphn0ewxlplxulmzhzgutzw50zxitywn0axzlihtcbiagyw5pbwf0aw9uoibmywrllwluidmwmg1zo1xufvxuxg4uzmfkzs1szwf2zs1hy3rpdmuge1xuicbhbmltyxrpb246igzhzgutb3v0idmwmg1zo1xufvxuxg5aa2v5znjhbwvzigzhzgutaw4ge1xuicawjsb7xg4gicagb3bhy2l0etogmcu7xg4gih1cblxuicaxmdalihtcbiagicbvcgfjaxr5oiaxmdalo1xuicb9xg59xg5cbkbrzxlmcmftzxmgzmfkzs1vdxqge1xuicawjsb7xg4gicagb3bhy2l0etogmtawjttcbiagfvxuxg4gidewmcuge1xuicagig9wywnpdhk6idalo1xuicb9xg59xg48l3n0ewxlplxuiiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcisxg4gicagxcj2dwuvc2vydmvylxjlbmrlcmvyxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3nlcnzlci1yzw5kzxjlci5lc20tynjvd3nlci5qc1wixg4gih1cbn0ilcjib21llnz1zsi6ijx0zw1wbgf0zt5cbiagpgrpdibjbgfzcz1cimhvbwvcij5cbiagicbib21lxg4gidwvzgl2plxupc90zw1wbgf0zt5cbiisikfib3v0lnz1zsi6ijx0zw1wbgf0zt5cbiagpcetlsbccmvha2luzybdb21tzw50ic0tplxuica8zgl2ignsyxnzpvwiywjvdxrcij5cbiagicbbym91dfxuica8l2rpdj5cbjwvdgvtcgxhdgu xg4ifq step to reproduce click the toggle button twice the component miss what be expect and component can be switch back and forth what be actually happen when switch to component with root comment break console do not have any warning system info no response any additional comment I think it should log a warning to admonish this usage if this be a limitation |
vuejscore | fix runtime dom these attrs should be set in chreateelement | Bug | close 6007 |
vuejscore | button type reset win t work correctly as various form field attribute be set through element property not as attribute | Bug | vue version 3 2 36 link to minimal reproduction sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcbmnvbnn0ig1zzya9ihjlzignjylcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxwpknsawnraw5nihrozsbyzxnldcbidxr0b24gc2hvdwxkihjldgfpbib0agugdmfsdwvzigfzihnldcbpbibive1mlibjbnn0zwfkigl0ignszwfycyb0agugzm9ybswgymvjyxvzzsbwdwugaxmgcmvtb3zpbmcgdghlifwic2vszwn0zwrciibldgmuigf0dhjpynv0zxmupc9wplxuicbcbiagpgzvcm0gbwv0ag9kpvwicg9zdfwiigfjdglvbj1cii9zb21lcgxhy2uvxci xg4gicagphnlbgvjdcbuyw1lpvwic2vszwn0vgvzdfwiplxuicagicagpg9wdglvbib2ywx1zt1cijfcij5vchrpb24gb25lpc9vchrpb24 xg4gicagica8b3b0aw9uihzhbhvlpvwimlwiihnlbgvjdgvkpm9wdglvbib0d288l29wdglvbj5cbiagicagidxvchrpb24gdmfsdwu9xcizxci b3b0aw9uihrocmvlpc9vchrpb24 xg4gicagpc9zzwxly3q xg5cbiagica8aw5wdxqgdhlwzt1cimnozwnrym94xcigbmftzt1cimnozwnrvgvzdfwiihzhbhvlpvwib25lxcigy2hly2tlzcavplxuicagidxpbnb1dcb0exblpvwidgv4dfwiihzhbhvlpvwidgv4dcbpbnb1dcb2ywx1zvwiic8 xg4gicagxg4gicagpgluchv0ihr5cgu9xcjyzxnldfwiplxuica8l2zvcm0 xg48l3rlbxbsyxrlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ifq step to reproduce optional make change to the form click the reset input what be expect the form field should be set to or stay at their initial value select option two checkbox check text text input value what be actually happen the select be set to first option and the other field be clear system info shell reproducible in sfc vuejs org code sandbox vue cli and custom build firefox chrome vivaldi window mac linux any additional comment inspect the code to see that the attribute select check and value text input value have be remove in the vue instance |
vuejscore | local variable reference in dev script setup don t work | Bug | link to minimal reproduction eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxubgv0ihggpsawo1xuznvuy3rpb24gaw5jkckgeyb4kysgfvxuznvuy3rpb24gc2hvdygpihsgywxlcnqoj3ggaxmgjyarihgpih1cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxkaxy xg4gicagpgj1dhrvbibay2xpy2s9aw5jpkluyyaod29ya3mppc9idxr0b24 icagifxuicagidxidxr0b24gqgnsawnrpxgrkz5jbmmgkgrvzxmgbm90ihdvcmsppc9idxr0b24 xg4gicagpgj1dhrvbibay2xpy2s9c2hvdz5tag93ihggdmfsdwugkgnvcnjly3qppc9idxr0b24 xg4gidwvzgl2piagicbcbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcjcbiagfvxufsj9 step to reproduce in dev mode try to use a local variable that be not a reference I e a plain value not an object nor array nor ref directly from a script setup template the link repro be a repro but not inside the sfc playground because it compile to non dev the repro have two button that increment a local variable and one to show its value in an alert box button that go through function with a capture inside setup function work button that manipulate the variable directly don t what be expect in build mode which be what sfc playground run click inc button increment the value by 1 as can be visualise with the third button what be actually happen in dev mode the non work button the one without a local function that capture the x variable do not increment the value neither would it read the correct value if that be a case the reason be that in dev mode for the dev tool a regular script setup object be build like so js const return prop emit x of course this just put a copy of the current value of local variable in the setup object any reference to this x value in template be totally disconnect from the variable in code to clarify why this work in build mode this be because the sfc compiler doesn t use a setup object at all but rather create a render function that immediately close over the local variable like so js let x 0 return ctx cache return openblock createelementblock div null createelementvnode button onclick cache 0 cache 0 event isref x x value x inc do not work system info shell system os window 10 10 0 19042 cpu 12 x64 intel r core tm i7 9850h cpu 2 60ghz memory 4 68 gb 15 79 gb binary node 16 6 0 c program file nodejs node exe yarn 1 22 10 appdata roam npm yarn cmd npm 7 19 1 c program file nodejs npm cmd browser edge spartan 44 19041 1266 0 chromium 101 0 1210 39 chromiumdev 103 0 1253 0 internet explorer 11 0 19041 1566 npmpackage vue 3 2 33 3 2 33 any additional comment this might be a bit ugly to fix I see two solution 1 the dev mode setup object should contain get set property that actually proxy local variable that be let not const 2 user js code be rewrite so that all return let local variable live on the return object from the start and all setup code reference these variable be rewrite to dereference that object that require modify the user code so it s quite more tricky than option 1 |
vuejscore | throw can not read property of undefined reading stop on component unmount and use nest watch | Bug | version 3 2 30 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcbmltcg9ydcbdb21wigzyb20gjy4vq29tcc52dwunxg5jb25zdcb2axnpymxlid0gcmvmkhrydwupxg5jb25zdcbsywjlbca9ihjlzignagvsbg8sihdvcmxkiscpxg48l3njcmlwdd5cbjx0zw1wbgf0zt5cbiagcgxlyxnlignsawnricdub2dnbgunigj1dhrvbiwgdg8gz2v0ihrocm93llxuxg4gidxociavplxuicbcbiagpgj1dhrvbibay2xpy2s9xcj2axnpymxlid0gixzpc2libgvcij5ub2dnbgu8l2j1dhrvbj5cbiagxg4gidxociavplxuicbcbiagpenvbxagdi1pzj1cinzpc2libgvciiavplxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3vucgtnlmnvbs9adnvll3j1bnrpbwutzg9tqdmumi4zmy9kaxn0l3j1bnrpbwutzg9tlmvzbs1icm93c2vylmpzxcjcbiagfvxufsisiknvbxaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgdg9szwysihdhdgnoih0gznjvbsandnvlj1xuxg5jb25zdcbub29wid0gkckgpt4ge31cblxuy29uc3qgchjvchmgpsbkzwzpbmvqcm9wcyh7xg4gige6ifn0cmluzyxcbiagyjogu3ryaw5nxg59kvxuxg53yxrjachcbiagdg9szwyochjvchmsicdhjyksxg4gich2lcbwdiwgb25jbnzhbglkyxrlksa9pib7xg4gicagy29uc3qgc3rvcca9ihdhdgnokhrvumvmkhbyb3bzlcanyicplcbub29wkttcbiagicbvbkludmfsawrhdguoc3rvcck7xg4gih0sxg4gihsgaw1tzwrpyxrloib0cnvlih1cbik7xg48l3njcmlwdd5cbjx0zw1wbgf0zt48l3rlbxbsyxrlpij9 step to reproduce 1 please click toggle button in demo you will see the error what be expect when the toggle button be click the component be unmounted normally what be actually happen toggle button then change visible to false then it will cause the to be unmount and throw error the issue be present in 3 2 30 and later |
vuejscore | v model on checkboxe no long work with truthy falsy value | Bug | version 3 2 33 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxuy29uc3qgzmlyc3rpchrpb24gpsbyzwyodhj1zsk7xg5jb25zdcbzzwnvbmrpchrpb24gpsbyzwyomsk7xg5jb25zdcb0aglyze9wdglvbia9ihjlzihcijfciik7xg4gifxuicbjb25zdcbkew5hbwljt3b0aw9uid0gcmvmkdapo1xupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpggxpknozwnrym94zxm8l2gxplxuica8bgfizww xg4gicagpgluchv0ihytbw9kzww9xcjmaxjzde9wdglvblwiihr5cgu9xcjjagvja2jvefwiplxuicagiekgc2hvdwxkigjlignozwnrzwqgkekgyw0gdhj1zslcbiagpc9sywjlbd5cbiagpgxhymvsplxuicagidxpbnb1dcb2lw1vzgvspvwic2vjb25kt3b0aw9uxcigdhlwzt1cimnozwnrym94xci xg4gicagssb0b28gc2hvdwxkigjlignozwnrzwqgkekgyw0gmslcbiagpc9sywjlbd5cbiagpgxhymvsplxuicagidxpbnb1dcb2lw1vzgvspvwidghpcmrpchrpb25ciib0exblpvwiy2hly2tib3hcij5cbiagicbjihrvbybzag91bgqgymugy2hly2tlzcaossbhbsbcijfciilcbiagpc9sywjlbd5cbiagpghyic8 xg4gidxsywjlbd5cbiagica8aw5wdxqgdi1tb2rlbd1cimr5bmftawnpchrpb25ciib0exblpvwiy2hly2tib3hcij5cbiagicbjigftigvkaxrhymxloia8aw5wdxqgdhlwzt1cinrlehrciib2lw1vzgvspvwizhluyw1py09wdglvblwiic8 xg4gidwvbgfizww xg4gifxupc90zw1wbgf0zt5cblxuphn0ewxlplxuicbsywjlbcb7xg4gicagzglzcgxhetogymxvy2s7xg59xg48l3n0ewxlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ifq step to reproduce 1 bind a non boolean truthy value to a checkbox use v model 2 observe that the checkbox be in fact not check what be expect v model at least in vue 2 use to work fine with checkboxe use truthy and falsy value instead of strict boolean value so I would expect this behavior to continue in vue 3 especially since this isn t list as a break change which it definitely be what be actually happen vue only check the checkbox if the correspond v model have the boolean value of true it ignore all else case in point I be work with an api that return boolean like value as 0 1 instead of true false for reason of sql this be never an issue with vue 2 I be aware of the true value and false value attribute but that shouldn t be necessary right |
vuejscore | duplicate key for transition group fragment when child have v if | Bug | version 3 2 33 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbiagaw1wb3j0iel0zw0gznjvbsbcii4vsxrlbs52dwvcilxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpfryyw5zaxrpb25hcm91cd5cbiagica8dgvtcgxhdgugdi1mb3i9xcioaxrlbswgawr4ksbvzibbj0enlcanqiddxcigomtlet1ciml0zw1cij5cbiagicagidxjdgvtpnt7iglkecb9ftoge3sgaxrlbsb9fte8l0l0zw0 xg4gicagica8sxrlbsb2lwlmpvwiawr4idwgmvwipnt7iglkecb9ftoge3sgaxrlbsb9fti8l0l0zw0 xg4gicagpc90zw1wbgf0zt5cbiagpc9ucmfuc2l0aw9ur3jvdxa xg48l3rlbxbsyxrlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vdw5wa2cuy29tl0b2dwuvcnvudgltzs1kb21amy4yljmzl2rpc3qvcnvudgltzs1kb20uzxntlwjyb3dzzxiuanncilxuicb9xg59iiwisxrlbs52dwuioii8dgvtcgxhdgu xg4gidxkaxy wzxzbg90pjwvc2xvdd5dpc9kaxy xg48l3rlbxbsyxrlpij9 step to reproduce have a |
vuejscore | keepalive dynamic include not restore state properly | Bug | version 3 2 33 reproduction link sfc vuejs org eyjbchaudnvlijoiphrlbxbsyxrlplxuica8zgl2plxuica8ynv0dg9uiebjbgljaz1cim9uq2xpy2tub2dnbgvcij5cbiagicbub2dnbgvcbiagpc9idxr0b24 xg4gicagpetlzxbbbgl2zsa6aw5jbhvkzt1cimfjdgl2zurpywxvz3ncij5cbiagicagidxjb21wb25lbnqgdi1pzj1cimntce5hbwvciia6axm9xcjjbxboyw1lxcigomtlet1cimntce5hbwuubmftzvwiieb2bm9kzs1tb3vudgvkpvwib25nb3vudentcfwiic8 xg4gicagpc9lzwvwqwxpdmu xg4gidwvzgl2plxupc90zw1wbgf0zt5cblxuphnjcmlwdd5cbmltcg9ydcb7ihjlziwgy29tchv0zwqsihjlywn0axzlih0gznjvbsandnvlj1xuaw1wb3j0ienvbxagznjvbsbcii4vq29tcc52dwvcijtcbmltcg9ydcbdb21wmibmcm9tifwili9db21wmi52dwvcijtcblxuzxhwb3j0igrlzmf1bhqge1xuicbuyw1loibcikfwcfwilfxuicbjb21wb25lbnrzoib7xg4gicagq29tccxcbiagicbdb21wmlxuicb9lfxuicbzzxr1ccgpihtcbiagicbjb25zdcbzag93q21wmsa9ihjlzih0cnvlkttcbiagicbjb25zdcbhy3rpdmveawfsb2dzid0gcmvhy3rpdmuow10po1xuicagignvbnn0igntce5hbwugpsbjb21wdxrlzcgoksa9pibzag93q21wms52ywx1zsa ienvbxagoibdb21wmik7xg4gicagznvuy3rpb24gb25dbglja1rvz2dszsgpihtcbiagicagihnob3ddbxaxlnzhbhvlid0gixnob3ddbxaxlnzhbhvlo1xuicagih1cbiagicbmdw5jdglvbibvbk1vdw50q21wkckge1xuicagicagy29uc3qge25hbwv9id0gy21wtmftzs52ywx1zvxuicagicagawygkgfjdgl2zurpywxvz3muzmluzcgoaxrlbskgpt4gaxrlbsa9pt0gbmftzskpihtcbiagicagicagcmv0dxjuo1xuicagicagfvxuicagicagy29uc29szs5sb2coj3b1c2hpbmcnlcbuyw1lkvxuicagicagywn0axzlrglhbg9ncy5wdxnokg5hbwupo1xuicagih1cbiagicbyzxr1cm4ge1xuicagicagywn0axzlrglhbg9ncyxcbiagicagigntce5hbwusxg4gicagicbvbknsawnrvg9nz2xllfxuicagicagb25nb3vudentcfxuicagih1cbiagfvxufvxupc9zy3jpchq iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumzmvzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ilcjdb21wlnz1zsi6ijx0zw1wbgf0zt5cblx0pgrpdj5cbiagicbdb21wb25lbnqgmvxuicagidxzcgfuihytawy9xcjzag93vghpbmdcij5uagluzye8l3nwyw4 xg4gicagpgj1dhrvbibay2xpy2s9xcjvbknsawnrqnv0dg9uxci xg4gicagicbtzxqgu2hvd1xuicagidwvynv0dg9uplxuica8l2rpdj5cbjwvdgvtcgxhdgu xg5cbjxzy3jpchq xg5pbxbvcnqgeybyzwysignvbxb1dgvklcbyzwfjdgl2zswgb25nb3vudgvkih0gznjvbsandnvlj1xuicbcbmv4cg9ydcbkzwzhdwx0ihtcbiagbmftztogxcjdb21wb25lbnrpbmvciixcbiagc2v0dxaoksb7xg4gicagy29uc3qgc2hvdya9ihjlzihmywxzzsk7xg4gicagy29uc3qgc2hvd1roaw5nid0gy29tchv0zwqokckgpt4gc2hvdy52ywx1zsk7xg4gicagznvuy3rpb24gb25dbglja0j1dhrvbigpihtcbiagicagihnob3cudmfsdwugpsahc2hvdy52ywx1zttcbiagicb9xg4gicagb25nb3vudgvkkcgpid0 ihtcbiagicagignvbnnvbguubg9nkcdnb3vudgluzycpo1xuicagih0po1xuicagihjldhvybib7xg4gicagicbzag93vghpbmcsxg4gicagicbvbknsawnrqnv0dg9uxg4gicagfvxuicb9xg59xg48l3njcmlwdd4ilcjdb21wmi52dwuioii8dgvtcgxhdgu xg5cddxkaxy xg4gicagq29tcg9uzw50idjcbiagpc9kaxy xg48l3rlbxbsyxrlplxuxg48c2nyaxb0plxuzxhwb3j0igrlzmf1bhqge1xuicbuyw1loibciknvbxbvbmvudfr3b1wilfxufvxupc9zy3jpchq in0 step to reproduce click the set show button in component 1 verify thing show click toggle button verify component 2 show click toggle button verify component1 with thing show click set show button verify thing do not hide what be expect when I click set show after perform the above step it should hide thing from be show what be actually happen set show be trigger but the value do not appear to be respect anymore as thing never go away no matter how many time set show be click |
vuejscore | transition use wrong leave to class when html comment exist as template root | Bug | version 3 2 31 reproduction link stackblitz com step to reproduce refer the stackblitz link and reproduce the issue by click on page a and page b navigation what be expect transition should work as expect and note by the transition name regardless of existence of comment I e page a should slide leave page b should slide right what be actually happen leave transition be not update for page component with comment page a slide right on leave transition |
vuejscore | circular component in vue3 typescript setup macro fail to build | Bug | version 3 2 25 reproduction link github com step to reproduce try and build the project npm run build or open it with vscode volar what be expect the project be build without any error what be actually happen the compiler return multiple error state that all property didn t exist run in dev mode work just fine |
vuejscore | certain prop be not convert from camelcase to kebab case when render | Bug | version 3 2 31 reproduction link github com step to reproduce certain popular aria attribute like label and expand get correctly convert from camelcase to kebab case but other like control and haspopup do not what be expect for behavior to be consistent either for vue to convert all prop back to kebab case or at least for it to convert all html support prop and not just some of they at random what be actually happen only some prop be be convert the behavior be inconsistent and unintuitive relate issue |
vuejscore | directive hook be inconsistent for component with text node | Bug | version 3 2 25 reproduction link stackblitz com step to reproduce create a component with a text node in the top level of the template and attach a custom directive to debug mount unmounted hook what be expect I expect hook to work normally or if they didn t to throw a warning like it happen for component with multiple root nodes what be actually happen the first mount hook seem to work fine but then unmounted hook don t work and mount be call twice in case you re wonder why would I need this sometimes I write at the top of component template and that s how I come across this issue it wasn t easy to pinpoint the source of the problem so this may bite other people as well |
vuejscore | keep alive component still update render watcher while be deactivate | Bug | version 3 2 30 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgchjvdmlkzswgc2hhbgxvd1jlzib9igzyb20gj3z1zsdcbiagaw1wb3j0ie9uzsbmcm9ticcul09uzs52dwunxg4gigltcg9ydcbud28gznjvbsanli9ud28udnvlj1xuxg5jb25zdcbtc2cgpsbyzwyoj0hlbgxvifdvcmxkiscpxg5jb25zdcbuid0gcmvmkdapxg5wcm92awrlkcdjb3vudgvyjywgbilcbiagxg4gignvbnn0ihbhz2ugpsbzagfsbg93umvmke9uzslcbiagznvuy3rpb24gdg9nz2xlugfnzsgpihtcbiagicbwywdllnzhbhvlid0gcgfnzs52ywx1zsa9pt0gt25lid8gvhdvidogt25lxg4gih1cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxwplxuicagienoyw5nzsbwywdlihrozw4gaw5jcmvtzw50igfuzcbjagvjayb0agugy29uc29szs5cbiagpc9wplxuica8ynv0dg9uiebjbgljaz1cim4rk1wiplxuicagieluy3jlbwvudfxuica8l2j1dhrvbj5cbiagxg4gidxocj5cbiagpgj1dhrvbibay2xpy2s9xcj0b2dnbgvqywdlxci xg4gicagq2hhbmdlihbhz2vcbiagpc9idxr0b24 xg4gifxuica8s2vlcefsaxzlplxuicagidxjb21wb25lbnqgomlzpvwicgfnzvwiic8 xg4gidwvs2vlcefsaxzlplxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59iiwit25llnz1zsi6ijxzy3jpchqgc2v0dxa xg5pbxbvcnqgeybpbmply3qgfsbmcm9ticd2dwunxg5cbmnvbnn0ig4gpsbpbmply3qoj2nvdw50zxinkvxuznvuy3rpb24gbg9nkckge1xuicbjb25zb2xllmxvzygnt25lihjlbmrlcmvkjylcbn1cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxwplxuicagieluie9uztogbjoge3sgbg9nkckgfhwgbib9fvxuicagidxidxr0b24gqgnsawnrpvwibisrxci xg4gicagicbjbmnyzw1lbnrcbiagica8l2j1dhrvbj5cbiagpc9wplxupc90zw1wbgf0zt4ilcjud28udnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7igluamvjdcb9igzyb20gj3z1zsdcblxuy29uc3qgbia9igluamvjdcgny291bnrlcicpxg5mdw5jdglvbibsb2coksb7xg4gignvbnnvbguubg9nkcdud28gcmvuzgvyzwqnkvxufvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpha xg4gicagsw4gvhdvoibuoib7eybsb2coksb8fcbuih19xg4gicagpgj1dhrvbibay2xpy2s9xcjukytcij5cbiagicagieluy3jlbwvudfxuicagidwvynv0dg9uplxuica8l3a xg48l3rlbxbsyxrlpij9 step to reproduce click increment click change page click increment observe the log what be expect log of one and then log for two only what be actually happen after change the page once the page one keep render while be inactive this have be confusing to many people but I couldn t find if this behavior be expect or not this also mean watcher be execute in deactivate branch enq9u7fu2zaq zurf8milhuw7lrblwydwhqfumhr6lmkrzokjgupjv 9r4q2vsdwmgqzcjb39x7vhh 34q7v0 2aihcli3xtwzboh 62okbrlbawb43rbhqtts0kezb12bzq9xvxcic1vh1eji8kagiin4qhkwa8d tt9j doqv5h9ifsuxgqmcqwlor4 g78kxwv l29smahqsopd9zjdqvr1inzffhcrchadway uyqkacu465jv zhkjarhfyvvut ulceaz7lwips7dlozjw9lbc vm dfyt3eaq0glbnspleodxa5vs4t8alg4or3rt7okbsf3zgskaehq7jasllqcwan8danfu2ox9ehshc8ebmu53a ybetjshb0c1oiwhx jbory6np uctx6y4j35imvt4mtcpxp6ubbbjbbyqih w3bb5y5juqwvk45xzth6rnyqrirgnme kpt0yrexbr34reqyq fe9cse2cedc1nb2js8ys5booxutkl1lves1m6dpmextzr 02hnutfyizmkrcxcleq6rvqhrx o8kh3gg17 wkmen1 7rg1tunqltzn19vhwnjo79otrvlvhcx694ukr82lob uabztiptnn5kas8d6qpz1xfwcm8i96zwwxdrswyejx 186 ppx5ulgv1pzv7nk7q9eqatjrtelenmmlrfpeb7a3ccin4rksi8s9faplxfrwq it also worth note that the component be deactivate render before be deactivate make it impossible to skip the render with likely incorrect datum |
vuejscore | too much recursion when object recursively reference each other | Bug | version 3 2 29 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlywn0axzlih0gznjvbsandnvlj1xuxg5jb25zdcbhid0ge307xg5jb25zdcbiid0ge307xg4gifxuy29uc3qgcgfyzw50id0ge1xuicbjaglszhjlbjogw2esigjdxg59o1xuxg5hlnbhcmvudca9ihbhcmvuddtcbmiucgfyzw50id0gcgfyzw50o1xuifxuy29uc3qgc3rhdgugpsbyzwfjdgl2zsh7xg4gihnlbgvjdgvksxrlbtogyiagxg59kttcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxzzwxly3qgdi1tb2rlbd1cinn0yxrllnnlbgvjdgvksxrlbvwiplxuicagidxvchrpb24gonzhbhvlpvwiyvwipke8l29wdglvbj5cbiagica8b3b0aw9uidp2ywx1zt1cimjcij5cpc9vchrpb24 xg4gidwvc2vszwn0plxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3vucgtnlmnvbs9adnvll3j1bnrpbwutzg9tqdmumi4yos9kaxn0l3j1bnrpbwutzg9tlmvzbs1icm93c2vylmpzxcjcbiagfvxufsj9 step to reproduce when launch the repro in the sfc playground you will immediately notice the error too much recursion there be no additional step require what be expect I expect to see no error what be actually happen in the sfc playground you will notice the error too much recursion when run it locally you might see something like this uncaught in promise rangeerror maximum call stack size exceed at function symbol hasinstance at isdate share esm bundler js 99c4 485 1 at looseequal share esm bundler js 99c4 386 1 at looseequal share esm bundler js 99c4 413 1 at looseequal share esm bundler js 99c4 413 1 at looseequal share esm bundler js 99c4 413 1 at looseequal share esm bundler js 99c4 413 1 at looseequal share esm bundler js 99c4 413 1 at looseequal share esm bundler js 99c4 413 1 at looseequal share esm bundler js 99c4 413 1 to I it look like vue be try to deep compare these object and do not track already visit one this be a data structure you might see e g when deal with tree like structure that be aware of their parent one solution would be to filter out the parent information but that could be non trivial when use more complex datum structure e g generate by a library |
vuejscore | potential memory leak with keep alive element hide early | Bug | version 3 2 28 reproduction link codesandbox io step to reproduce 1 open memory panel in chrome devtool run the garbage collection then take heap snapshot of mbwyj instance 2 click twice on the toggle button 3 run the garbage collection and take a heap snapshot again filter by detach 4 click a pair number of time on the toggle button 3 run the garbage collection and take a heap snapshot again filter by detach what be expect the number of detach element should not increase after each pair of click what be actually happen the number of detach element be increase after each pair of click screenshot 2022 01 21 23 02 48 funnily the problem do not happen if either of this be do comment the beforeunmount in beforeunmountcomponent move the from app vue to within the keep alive of keepalivecomponent might be relate to and relate to |
vuejscore | memory leak in hoist static | Bug | version 3 2 26 reproduction link github com step to reproduce 1 open dist index html 2 click click button three time 3 open memory panel in chrome devtool then take heap snapshot then search bigdata what be expect old component instance can reacyle what be actually happen old component instance not reacyle hoist num hoisted el dom static hoist will create a hoisted variable in the closure and later set dom to hoist el when render if there be event listener in the component the component instance can not be recycle result in a memory leak |
vuejscore | the withdefault function lose argument when assign a function default value | Bug | version 3 2 26 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1ccbsyw5npvwidhncij5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcbmnvbnn0ihbyb3bzid0gd2l0aerlzmf1bhrzkgrlzmluzvbyb3bzphtcbiagzm4 oiaobmftztogc3ryaw5nksa9pib2b2lkxg59pigplcb7xg4gigzukg5hbwu6ihn0cmluzykge1xuicagihjldhvybibuyw1llnrvvxbwzxjdyxnlkclcbiagfvxufslcbmnvbnnvbguubg9nkhbyb3bzlmzukvxulyoqxg50agugchjvchmuzm4gaxncbmrlzmf1bhqoksb7xg4gicagcmv0dxjuig5hbwuudg9vchblcknhc2uokvxuicb9xg4ql1xupc9zy3jpchq xg5jb25zdcbtc2cgpsbyzwyojycpxg48dgvtcgxhdgu xg4gidxomt57eybmbihtc2cpih19pc9omt5cbiagpgluchv0ihytbw9kzww9xcjtc2dcij5cbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcjcbiagfvxufsj9 step to reproduce typescript const prop withdefault defineprop fn name string void fn name string return name touppercase console log prop fn what be expect return the correct default value what be actually happen function default lose argument |
vuejscore | suspense incorrect update behavior if default root node be slot | Bug | version 3 2 26 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbiagaw1wb3j0ihsgcmvmih0gznjvbsandnvlj1xuxhrpbxbvcnqgu3vzcgvuc2vxcmfwcgvyigzyb20gjy4vu3vzcgvuc2vxcmfwcgvylnz1zsdcbiagaw1wb3j0iefzew5jq29tccbmcm9ticcul0fzew5jq29tcc52dwunxg4gignvbnn0iglkid0gcmvmkdapxg4gifxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpggxplnsb3r0zwqgu3vzcgvuc2ugvgvzddwvade xg4gidxzdxnwzw5zzs13cmfwcgvyplxuicbcdfx0pgfzew5jlwnvbxagomlkpvwiawrciia6a2v5pvwiawrcij48l2fzew5jlwnvbxa xg4gidwvc3vzcgvuc2utd3jhchblcj5cbiagpgj1dhrvbibay2xpy2s9xcjpzcsrxci sw5jcmvhc2ugswq8l2j1dhrvbj5cbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumjyvzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ilcjtdxnwzw5zzvdyyxbwzxiudnvlijoiphrlbxbsyxrlplxuica8u3vzcgvuc2u xg4gicagphrlbxbsyxrlicnkzwzhdwx0piagicagxg4gicagicagidxzbg90ig5hbwu9xcjkzwzhdwx0xci pc9zbg90plxuicagidwvdgvtcgxhdgu xg4gicagphrlbxbsyxrlicnmywxsymfjaz5cbiagicagidxzbg90ig5hbwu9xcjmywxsymfja1wipibezwzhdwx0iexvywrpbmcgtwvzc2fnzs4ulia8l3nsb3q xg4gicagpc90zw1wbgf0zt5cbiagpc9tdxnwzw5zzt5cbjwvdgvtcgxhdgu xg5cbjxzy3jpchqgc2v0dxagplxuxg4gifxupc9zy3jpchq iiwiqxn5bmndb21wlnz1zsi6ijx0zw1wbgf0zt5cbiagpggxplxuicage3t0axrszx19xg4gidwvade xg48l3rlbxbsyxrlplxuxg48c2nyaxb0ihnldhvwid5cblx0znvuy3rpb24gc2xlzxaobxmpihtcbiagicbyzxr1cm4gbmv3ifbyb21pc2uokhjlc29sdmupid0 ihtcbiagicagihnldfrpbwvvdxqocmvzb2x2zswgbxmpo1xuicagih0po1xuicb9xg4gifxuicbjb25zdcb7iglkih0gpsbkzwzpbmvqcm9wcyh7xg4gicagawq6ie51bwjlclxuicb9kvxuicbcbiagyxn5bmmgznvuy3rpb24gz2v0vgl0bguoksb7xg4gicagyxdhaxqgc2xlzxaomjawmck7xg4gicagcmv0dxjuifwivgl0bgugxcigkybpzfxuicb9ifxuicbcbiagy29uc3qgdgl0bgugpsbhd2fpdcbnzxruaxrszsgpxg4gifxuxg4gifxupc9zy3jpchq in0 step to reproduce 1 wrap the suspense component use slot 2 use the wrap suspense component wsc to suspend an async root node 3 destroy the root node and replace it with a new async root node what be expect the old root node should stay until the new root node be load what be actually happen the old root node be destroy before the new root node be load I want to wrap the suspense component to have a default loading error handle behavior which be probably a common thing to do when you be use suspense |
vuejscore | conditional rendering cause to trigger css transition | Bug | version 3 2 26 reproduction link sfc playground eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbiagaw1wb3j0ihsgcmvmlcbjb21wdxrlzcwgd2f0y2hfzmzly3qgfsbmcm9ticd2dwunxg4gigltcg9ydcbsb3cgznjvbsanli9sb3cudnvlj1xuxg4gignvbnn0igl0zw1zid0gnta7xg4gignvbnn0igl0zw1zugvyugfnzsa9idewo1xuicbjb25zdcb0b3rhbfbhz2vzid0gtwf0ac5jzwlskgl0zw1zic8gaxrlbxnqzxjqywdlkttcbiagy29uc3qgy3vycmvudfbhz2ugpsbyzwyomslcbiagy29uc3qgzgf0ysa9ifsuli5uzxcgqxjyyxkoaxrlbxmpxs5tyxaokf8sigluzgv4ksa9piaoe1xuicagiglkoibpbmrlecaridesxg4gicagzw5hymxlzdogdhj1zsxcbiagfskpxg4gignvbnn0ihbhz2veyxrhid0gy29tchv0zwqokckgpt4ge1xuicagignvbnn0ihn0yxj0id0gkgn1cnjlbnrqywdllnzhbhvlic0gmsapicogaxrlbxnqzxjqywdlxg4gicbcdhjldhvybibkyxrhlnnsawnlkhn0yxj0lcbzdgfydcarigl0zw1zugvyugfnzslcbiagfslcblxuicbjb25zdcbzzxrqywdlid0gbmv4dca9pib7xg4gicagy3vycmvudfbhz2uudmfsdwugpsbnyxrolm1pbihnyxrolm1hechuzxh0lcaxkswgdg90ywxqywdlcyk7xg4gih1cbiagxg4gignvbnn0ievoqujmrv9tuefox1nxqvagpsb0cnvlifxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpgrpdj5cbiagica8dgfibgu xg4gicagica8dgjvzhk xg4gicagicagidxsb3cgdi1mb3i9xcjpdgvtigluihbhz2veyxrhxcigomtlet1ciml0zw0uawrciia6axrlbt1ciml0zw1ciiavplxuicagicagpc90ym9ket5cbiagica8l3rhymxlplxuxg4gicagpha ugfnztoge3sgy3vycmvudfbhz2ugfx08l3a xg5cbiagica8b2w xg4gicagica8bgkgdi1mb3i9xcjwywdligluihrvdgfsugfnzxnciia6a2v5pvwicgfnzvwiplxuicagicagica8dgvtcgxhdgugdi1pzj1cikvoqujmrv9tuefox1nxqvbcij5cbiagicagicagica8c3bhbib2lwlmpvwicgfnzsa9pt0gy3vycmvudfbhz2vciibjbgfzcz1ciml0zw0gywn0axzlxci e3sgcgfnzsb9ftwvc3bhbj5cbiagicagicagica8ynv0dg9uifxuicagicagicagicagdi1lbhnliebjbgljaz1cinnldfbhz2uocgfnzslciibcbiagicagicagicagignsyxnzpvwiaxrlbvwixg4gicagicagicagplxuicagicagicagifx0e3sgcgfnzsb9fvxuicagicagicagidwvynv0dg9uplxuicagicagica8l3rlbxbsyxrlplxuicagicagica8dgvtcgxhdgugdi1lbhnlplxuicagicagicbcddxidxr0b24gxg4gicagicagicagicbay2xpy2s9xcjzzxrqywdlkhbhz2upxcjcbiagicagicagicagidpjbgfzcz1cilsnaxrlbscsihbhz2ugpt09ign1cnjlbnrqywdlicymicdhy3rpdmunxvwixg4gicagicagicagplxuicagicagicagifx0e3sgcgfnzsb9fvxuicagicagicagidwvynv0dg9uplxuicagicagica8l3rlbxbsyxrlplxuicagicagpc9sat5cbiagica8l29splxuxhrcdfxuicagidxicj5cbiagica8ynv0dg9uiebjbgljaz1cinnldfbhz2uoy3vycmvudfbhz2uglsaxkvwipnbyzxy8l2j1dhrvbj5cbiagica8ynv0dg9uiebjbgljaz1cinnldfbhz2uoy3vycmvudfbhz2ugkyaxkvwipm5lehq8l2j1dhrvbj5cbiagpc9kaxy xg48l3rlbxbsyxrlplxuxg48c3r5bgugc2nvcgvkplxuicaqlcaqojpizwzvcmusico6omfmdgvyihtcbiagicbib3gtc2l6aw5noibib3jkzxitym94o1xuicb9xg4gifxuicbvbcwgbgkge1xuicagig1hcmdpbjogmdtcbiagicbwywrkaw5noiawo1xuicagigxpc3qtc3r5bgu6ig5vbmu7xg4gih1cblxuicbvbcb7xg4gicagzglzcgxhetogzmxledtcbiagfvxuxg4gic5pdgvtihtcbiagicb3awr0adogmmvto1xuicagighlawdoddogmmvto1xuicagigrpc3bsyxk6igjsb2nro1xuicagig1hcmdpbjogmdtcbiagicbwywrkaw5noiawo1xuicagigjvcmrlci1yywrpdxm6iduwjttcbiagicbib3jkzxi6ida7xg4gicagymfja2dyb3vuzdogi0vgrjbgmjtcbiagicbmb250oibpbmhlcml0o1xuicagignvbg9yoiajmdawo1xuicagihrlehqtywxpz246ignlbnrlcjtcbiagicbsaw5llwhlawdoddogmmvto1xuicagign1cnnvcjogcg9pbnrlcjtcbiagfvxuicbcbiaglml0zw0uywn0axzlihtcbiagicbiywnrz3jvdw5koiajmdi4ywzmo1xuicagignvbg9yoiajzmzmo1xuicagihbvaw50zxitzxzlbnrzoibub25lo1xuicb9xg48l3n0ewxlplxuiiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcjcbiagfvxufsisiln3axrjac52dwuioii8c2nyaxb0ihnldhvwplxuicbpbxbvcnqgeybyzwysignvbxb1dgvklcb2tw9kzwxdagvja2jvecb9igzyb20gj3z1zsdcbiagxg4gigrlzmluzvbyb3bzkfsnbw9kzwxwywx1zsddkvxuicbjb25zdcblbwl0id0gzgvmaw5lrw1pdhmowyd1cgrhdgu6bw9kzwxwywx1zsddkvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpgxhymvsplxuicbcddxpbnb1dcbcbiagicagihytbw9kzwwty2hly2tib3g9xcjtb2rlbfzhbhvlxcjcbiagicagieb1cgrhdgu6bw9kzwxwywx1zt1cinzhbhvlid0 igvtaxqoj3vwzgf0ztptb2rlbfzhbhvljywgdmfsdwupxcjcbiagicagihr5cgu9xcjjagvja2jvefwiifxuicagic8 xg4gicagphnsb3q pc9zbg90plxuica8l2xhymvsplxupc90zw1wbgf0zt5cblxuphn0ewxlihnjb3blzd5cbiagkiwgkjo6ymvmb3jllcaqojphznrlcib7xg4gicagym94lxnpemluzzogym9yzgvylwjvedtcbiagfvxuicbcbiagkib7ig1hcmdpbjogmdsgcgfkzgluzzogmdsgfvxuicbcbiagbgfizwwge1xuicagic0tdgh1bwitc2l6ztogmjbwedtcbiagicatlxryywnrlxnpemu6ignhbgmodmfykc0tdgh1bwitc2l6zskgkiaykttcbiagicbkaxnwbgf5oibmbgv4o1xuicagigfsawdulwl0zw1zoibjzw50zxi7xg4gicagz2fwoiaxy2g7xg4gicagdxnlci1zzwxly3q6ig5vbmu7xg4gicagy3vyc29yoibwb2ludgvyo1xuicb9xg4gifxuicbpbnb1dcb7xg4gicagls10ahvtyi1wb3npdglvbjogm3b4o1xuicagic0tdgh1bwity29sb3i6icnkzgq7xg4gicagzglzcgxhetogz3jpzdtcbiagicbhbglnbi1pdgvtczogy2vudgvyo1xuicagigzszxgtc2hyaw5roiawo1xuicagigjvcmrlcjogmnb4ihnvbglkicnkzgq7xg4gicagaw5saw5llxnpemu6ihzhcigtlxryywnrlxnpemupo1xuicagigjsb2nrlxnpemu6ihzhcigtlxrodw1ilxnpemupo1xuicagigjvcmrlci1yywrpdxm6ihzhcigtlxrodw1ilxnpemupo1xuicagigjvcmrlci1ib3g6ignvbnrlbnqtym94o1xuicagigfwcgvhcmfuy2u6ig5vbmu7xg4gicagcg9pbnrlci1ldmvudhm6ig5vbmu7xg4gicagdg91y2gtywn0aw9uoibwyw4tettcbiagicbncmlkoibbdhjhy2tdidfmci9bdhjhy2tdidfmcjtcbiagfvxuicbcbiagaw5wdxq6omjlzm9yzsb7xg4gicagy29udgvuddogxcjcijtcbiagicbncmlklwfyzwe6ihryywnro1xuicagiglubgluzs1zaxploibjywxjkhzhcigtlxrodw1ilxnpemupic0gnnb4kttcbiagicbibg9jay1zaxploibjywxjkhzhcigtlxrodw1ilxnpemupic0gnnb4kttcbiagicbjdxjzb3i6ihbvaw50zxi7xg4gicagcg9pbnrlci1ldmvudhm6igf1dg87xg4gicagymfja2dyb3vuzdogdmfykc0tdgh1bwity29sb3ipo1xuicagigjvcmrlci1yywrpdxm6iduwjttcbiagicb0cmfuc2zvcm06ihryyw5zbgf0zvgodmfykc0tdgh1bwitcg9zaxrpb24pkttcbiagicb0cmfuc2l0aw9uoib0cmfuc2zvcm0gljnzo1xuicb9xg4gifxuicbpbnb1ddpjagvja2vkihtcbiagxhqtlxrodw1ilxbvc2l0aw9uoibjywxjkch2yxiols10cmfjay1zaxplksatidzweckglsaxmdalkttcbiagicatlxrodw1ilwnvbg9yoiajmdi4ywzmo1xuicb9xg48l3n0ewxlpiisiljvdy52dwuioii8c2nyaxb0ihnldhvwplxuicbpbxbvcnqgeybvbk1vdw50zwqsig9uvw5tb3vudgvkih0gznjvbsandnvlj1xuicbpbxbvcnqgu3dpdgnoigzyb20gjy4vu3dpdgnolnz1zsdcbiagxg4gignvbnn0ihsgaxrlbsb9id0gzgvmaw5luhjvchmowydpdgvtj10pxg4gifxuicbvbk1vdw50zwqokckgpt4ge1xuicagignvbnn0iglkid0gaxrlbs5pzdtcbiagicbjb25zb2xllmxvzygnbw91bnrlzccsiglkkvxuicagig9uvw5tb3vudgvkkcgpid0 ihtcbiagicagignvbnnvbguubg9nkcd1bm1vdw5lzccsiglkkvxuicagih0pxg4gih0pxg48l3njcmlwdd5cblxuphrlbxbsyxrlplxuxhq8dhi xg4gicagphrkpnt7igl0zw0uawqgfx08l3rkplxuicagidx0zd48u3dpdgnoidptb2rlbc12ywx1zt1ciml0zw0uzw5hymxlzfwiic8 pc90zd5cbiagpc90cj5cbjwvdgvtcgxhdgu xg5cbij9 step to reproduce change page use pagination button not prev next what be expect switch should not animate when be mount what be actually happen for some reason the switch be animate when be mount idk why because its value be always set to true this bug be relate to the fact that inside the pagination I conditionally render either a button or a span tag line 38 if you set enable span swap to false to disable conditional rendering or use prev next button to change the page then this bug disappear also I couldn t reproduce it in the late firefox version only in the late chrome chrome canary |
vuejscore | unhandled error during execution of scheduler flush when render component in a transition group that have a v if directive | Bug | version 3 2 26 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcbmltcg9ydcbcyxigznjvbsanli9cyxiudnvlj1xuicbcbmnvbnn0igl0zw1zid0gcmvmkftdkvxuy29uc3qgzm9vid0gcmvmkftdkvxuy29uc3qgymfyid0gcmvmkftdkvxuxg5zzxruaw1lb3v0kcgpid0 ihtcbiagaxrlbxmudmfsdwugpsbbj2enlcanyicsicdjj11cbn0sidiwmdapxg5zzxruaw1lb3v0kcgpid0 ihtcbiagzm9vlnzhbhvlid0gwydhjywgj2inlcanyyddxg59lcayntawkvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagphryyw5zaxrpb24tz3jvdxagbmftzt1cinrlc3rciib0ywc9xcjkaxzciibhchblyxi xg4gifx0pgrpdibjbgfzcz1cimjsb2nrxcigdi1mb3i9xcjpdgvtigluigl0zw1zxcigomtlet1ciml0zw1cij5cbiagicagicb7e2l0zw19fsagicagicagicagicagicagicagicagicagicagicagicagifxuicagidwvzgl2plxuicagifxuicagidxkaxygy2xhc3m9xcjibg9jaybibg9jay1ibhvlxcigdi1pzj1cimzvby5szw5ndghciibrzxk9xcjmb29cij5cbiagicagicbgb28gaxmgagvyzvxuicagidwvzgl2plxuicagifxuicagidxiyxiga2v5pvwiymfyxciglz5cbiagpc90cmfuc2l0aw9ulwdyb3vwplxupc90zw1wbgf0zt5cbjxzdhlszt5cbi5ibg9jayb7xg4gihbhzgrpbmc6idewchg7xg4gigjhy2tncm91bmq6ihjlzdtcbiagbwfyz2lulwjvdhrvbtognxb4o1xufvxuicauymxvy2stymx1zsb7xg4gicagicbiywnrz3jvdw5koibibhvlo1xuicb9xg4udgvzdc1lbnrlci1hy3rpdmusic50zxn0lwxlyxzllwfjdgl2zsb7xg4gihryyw5zaxrpb246ig9wywnpdhkgljnzigvhc2u7xg59xg4udgvzdc1lbnrlci1mcm9tlcaudgvzdc1szwf2zs10byb7xg4gig9wywnpdhk6ida7xg59xg48l3n0ewxlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ilcjcyxiudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxuy29uc3qgymfyid0gcmvmkftdkvxuxg5zzxruaw1lb3v0kcgpid0 ihtcbiagymfylnzhbhvlid0gwydhjywgj2inlcanyyddxg59lcazmdawkvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpgrpdibjbgfzcz1cimjsb2nrigjsb2nrlwdyzwvuxcigdi1pzj1cimjhci5szw5ndgggpiawxci xg4gicagicbcyxigaxmgagvyzvxuicagpc9kaxy xg48l3rlbxbsyxrlplxuphn0ewxlplxulmjsb2nrihtcbiagcgfkzgluzzogmtbwedtcbiagymfja2dyb3vuzdogcmvko1xuicbtyxjnaw4tym90dg9toia1chg7xg59xg4gic5ibg9jay1ncmvlbib7xg4gicagicbiywnrz3jvdw5koibncmvlbjtcbiagfvxupc9zdhlszt4ifq step to reproduce I be use a transition group as follow vue within it I have a list of custom component if I apply a v if on these component within the parent template everything work as expect vue both foo and bar be load asynchronously and the component appear correctly with a transition animation as soon as the item be load and available however I try to refactor this to let the component load the item themselves and if I move the v if into the child component still on the outer most html element as follow vue this however trigger a series of error in the console unhandled error during execution of render function unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at typeerror child el getboundingclientrect be not a function what be expect that if use a v if inside of a child component which be list in a transition group this work as expect what be actually happen the error as above be throw and v for some of the component in the transition group fail to render try to render component in a transition group and govern their appearance internally in the component instead of externally in the parent component to reproduce in the playground remove the v if condition on the bar vue component to make the example work then put it back to trigger the error |
vuejscore | v once and unmount callback possible memory leak | Bug | version 3 2 26 reproduction link codesandbox io step to reproduce click on the toggle button at least twice what be expect console statement say that the othercmponent be unmounted destroy be show along with the mount statement what be actually happen only the mount statement be show this be behave differently in vue2 as the destroy callback be call see this might also be relate to this external issue I think I can see evidence of something similar with vue router and generally it might introduce memory leak when use component that be not specifically write to account for the beforeunmount unmounted not be call please do let I know if this be not an issue but just a documentation miss be it specify somewhere or should it be or if this be just my misunderstanding |
vuejscore | suspend component transition | Bug | version 3 2 26 reproduction link sfc eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbiagaw1wb3j0ienvbxbvbmvudcbmcm9ticcul0nvbxaudnvlj1xuicbpbxbvcnqgulzpzxcgznjvbsanli9svmlldy50cydcbiagaw1wb3j0ihsgc2hhbgxvd1jlziwgchjvdmlkzswgb25nb3vudgvklcbtyxjrumf3ih0gznjvbsandnvlj1xuicbcbiagy29uc3qgdmlldya9ihnoywxsb3dszwyokvxuicbcbiagchjvdmlkzsgndmlldycsihzpzxcpxg4gifxuicbzzxruaw1lb3v0kcgpid0 ihtcbiagicb2awv3lnzhbhvlid0gq29tcg9uzw50xg4gih0siduwmclcblxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpfjwawv3ihytc2xvdd1cinsgq29tcg9uzw50ih1cij5cblx0phryyw5zaxrpb24gbmftzt1cimzhzgutdg9wxcigbw9kzt1cim91dc1pblwiplxuicagicagicagidxzdxnwzw5zzsb0aw1lb3v0pvwimfwiplxuicagicagicagicagphrlbxbsyxrlicnkzwzhdwx0plxuicagicagicagicagica8y29tcg9uzw50ihytawy9xcjdb21wb25lbnrciia6axm9xcjdb21wb25lbnrciiavplxuicagicagicagicagpc90zw1wbgf0zt5cbiagicagicagicagidx0zw1wbgf0zsajzmfsbgjhy2s xg4gicagicagicagicagidxkaxy tg9hzgluzy4uli48l2rpdj5cbiagicagicagicagidwvdgvtcgxhdgu xg4gicagicagicagpc9zdxnwzw5zzt5cbiagicagicagpc90cmfuc2l0aw9uplxuicagidwvulzpzxc xg48l3rlbxbsyxrlplxuxg48c3r5bgugc2nvcgvkplxulmzhzgutdg9wlwvudgvylwfjdgl2zsb7xg4gihryyw5zaxrpb246igfsbcawljlzo1xufvxulmzhzgutdg9wlwxlyxzllwfjdgl2zsb7xg4gihryyw5zaxrpb246igfsbcawljlzo1xufvxulmzhzgutdg9wlwvudgvylwzyb20ge1xuicbvcgfjaxr5oiawo1xuicb0cmfuc2zvcm06ihryyw5zbgf0zvkomzvweck7xg59xg4uzmfkzs10b3atbgvhdmutdg8ge1xuicbvcgfjaxr5oiawo1xuicb0cmfuc2zvcm06ihryyw5zbgf0zvkoltm1chgpo1xuicbkaxnwbgf5oibub25lo1xufvxupc9zdhlszt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59iiwiq29tcc52dwuioii8c2nyaxb0ihnldhvwplxuaw1wb3j0ihsgcmvmih0gznjvbsbcinz1zvwio1xuznvuy3rpb24gz2v0rgf0ysgpihtcbiagcmv0dxjuig5ldybqcm9taxnlkchyzxnvbhzllcbyzwply3qpid0 ihtcbiagicbzzxruaw1lb3v0kcgpid0 ihtcbiagicagihjlc29sdmuoxcjva1wikttcbiagicb9lcaxmdawkttcbiagfsk7xg59xg5cbmnvbnn0igrhdgegpsbhd2fpdcbnzxreyxrhkck7xg5cbi8vy29uc3qgzgf0ysa9idfcbjwvc2nyaxb0plxuphrlbxbsyxrlplxuica8zgl2plxuicagidxomz5db21wmto8l2gzplxuicagidxzcgfuplxuicagicage3sgzgf0ysb9fvxuicagidwvc3bhbj5cbiagpc9kaxy xg48l3rlbxbsyxrlpiisiljwawv3lnrzijoiaw1wb3j0ihsgaw5qzwn0lcbolcbkzwzpbmvdb21wb25lbnqgfsbmcm9ticd2dwunxg5cbmv4cg9ydcbkzwzhdwx0igrlzmluzunvbxbvbmvudch7xg4gihnldhvwkf9wlcb7ihnsb3rzih0pihtcbiagicbjb25zdcbwawv3q29tcg9uzw50id0gaw5qzwn0kcd2awv3jylcblxuicagihjldhvybiaoksa9pib7xg4gicagicbjb25zdcbdb21wb25lbnqgpsbwawv3q29tcg9uzw50lnzhbhvlxg4gicagy29uc3qgy29tcg9uzw50id0gq29tcg9uzw50icymiggoq29tcg9uzw50kvxuxg4gicagcmv0dxjuichcbiagicagic8vihvzzsbbmf0gdg8gcmv0dxjuig9ubhkgb25lignoawxkxg4gicagicbzbg90cy5kzwzhdwx0khsgq29tcg9uzw50oibjb21wb25lbnqgfslbmf1cbiagicapxg4gicagfvxuicb9lfxufslcblxuin0 step to reproduce 1 open link 2 observe the animation happen only for loading what be expect 1 transition work with suspense default slot 2 and the normal component what be actually happen 1 transition only work with suspense fallback slot not the default slot 2 the normal component not top await loss transition animation |
vuejscore | inline svg state be break doesn t revert back | Bug | version 3 2 24 reproduction link codesandbox io step to reproduce create a component with a name slot use the component with v if v else on the name template on the if and else add 2 different svg inline svg svg when the state change the first time it work when you change again the state it doesn t work it keep display the old svg but other part of the component like text be display correctly I put this example in the codesandbox example see helloworld vue 1 you will see svg 2 click first time it will change to check mark 3 click again the text change but not the svg what be expect render the correct svg if state change the 2nd and 3rd time etc what be actually happen the svg state doesn t change it display the wrong svg of the old state forever but the text change correctly we have a big application that we be try to upgrade to vue 3 we get this warning and error on our app the code be work fine in vue 2 warning unhandled error during execution of scheduler flush this be likely a vue internal bug error uncaught in promise typeerror right hand side of in should be an object get null shouldsetasprop patchprop patchprop patchelement processelement patch patchkeyedchildren patchchildren in the example of codesandbox I provide couldn t really reproduce the error but it still doesn t work as expect |
vuejscore | watcheffect should not track watch s callback when the instance be not mount | Bug | version 3 2 23 reproduction link stackblitz com step to reproduce 1 change the select to key2 option the select value be still key because the watcheffect have be call typescript watcheffect console log watcheffect formdata value option 0 value and I find that the formdata value be track by watcheffect I think that be a bug because I don t get the value of formdata value in watcheffect and it shouldn t be track so I find the problem in the source code here be the code typescript from l353 if instance instance ismounte queuepreflushcb job else with pre option the first call must happen before the component be mount so it be call synchronously job if the instance be not mount watch s callback will be call sync so in watcheffect when I change the value of formdata value it will trigger watch s callback sync and then it will be track the formdata in this effect I think this be a bug therefore when first click the option key2 of select it will still the key option and when you second click the option key2 it can be change corrently the watch s callback will call async because the instance have be mount what be expect watcheffect should not track watch s callback when the instance be not mount what be actually happen watcheffect track watch s callback when the instance be not mount I think it can be fix in this way typescript if instance instance ismounte queuepreflushcb job else with pre option the first call must happen before the component be mount so it be call synchronously pausetracke job resettracke |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.