skirtle
skirtle
#7809 seems similar, though this PR appears more comprehensive.
I don't think there's a bug here. The exact execution order of `mounted`/`onMounted` isn't documented and I don't see a compelling reason why a global mixin should be given priority....
I was just playing with this and it seems to break typing in values via the keyboard: - [Playground](https://deploy-preview-7786--vue-sfc-playground.netlify.app/#eNp9kUFPAjEQhf/KZC5ogksMN7KQqOGgBzXqsReyO0Cx2zbtFDGb/e9OS0APhtv0vTfTb9oe77yv9olwhnVsgvYMkTj5hbK68y4w9BBoDQOsg+tgJNGRsso2zkaGFubZvbLJmGtl68lxhDTLganzZsUkJ4B6e7voe2kYhnoiddG09Ylhf9O5lkzVSnausFUI/O1LKYpCydaT8zAcI0e5fa031S46K+B9HqawcZ3XhsKLZy10CmdQnOytjHFfT0XjkGh80pstNZ//6Lt4yJrC10CRwl4wzh6vwob4aC/fn+kg9dmUVZKR9AXzjaIzKTMeY/fJtoL9J1doH8vza7v5iMsDk42npTJoTg4lr1C+5OHC6r+402pa+pQdcPgB3genJw==) Testing in Chrome and Firefox, it seems to be broken in...
I was wondering about some other edge cases. I'm not sure whether these necessarily impact this PR, but I thought they were worth considered before it's merged. I put together...
I think we may need to make a distinction between properties and attributes here. The original issue was specifically about properties, not attributes. I think having default prop values reflected...
While the initial hydration is no longer throwing an error, it seems that subsequent updates still fail: - [Playground](https://deploy-preview-13396--vue-sfc-playground.netlify.app/#__SSR__eNp9kU9PAjEQxb9K0wuaIHvQE1mMf0KiHtQox17WMguFbtu0UyAh+92dtggcDLfte783+6bd80fnRpsIfMzrIL1yyAJgdPfCqM5Zj2zPPLSsZ623HRsQOhBGGGlNIHRpt2ySgCv0Ea6FqasyhfJ0QOicbhDoxFg9840JCpU1rHEOGp9lMoK2yDY3qp0InkYKzqoSqU6ZIvxERMo/SK3k+oBTg7bRAQQ/DHxRcyjxgpNcV2dd+JBjoA1atRitgjW0/D7xgkvbOaXBf7j0yyD4mGUneY3WdvuWtbTs8E+XS5Drf/RV2CVN8E8PAfyG+h09bPwCsNjT73fY0ffR7Ow8aqIvmF8QrI6pY8GeoplT7TMut33NT6jMYhamOwS6ycNSqWgi+8wLTs/6fGH1U93b0V3OCdPz/hdghb5Z) There are also problems in this case, which doesn't use `appear`,...
What do you think about this case, with the `Transition` wrapped in a component? - [Playground](https://deploy-preview-13396--vue-sfc-playground.netlify.app/#__SSR__eNp9UstqwzAQ/BWhSy7BPrSnYAptyaGFPmhz1EXYm1SpLAlp7RqC/70rOQ/bhNykmdlhtKMDf3QuaxvgK16E0iuHLAA27kEYVTvrkb3ZSuqNlyYoVNawrbc1W2T5DI8mC2GKfHChebog1E5LBLoxVswmEkhw0BZZPkjmroQW+ciFLzmG0pqt2mX7YA3FPsRBwUtbO6XBf7g4FwRfscRETmpt/14Thr6B5Qkvf6D8vYLvQxcxwT89BPAtCH7mUPod4ECvv9+ho/OZrG3VaFLfIL8gWN3EjIPsqTEVxR7pUtqXtHxldpuw7hBoHcdHxaBR2Se94LT25xtPv8S9y+7TnDA9bfFKe/ELTAurVHsqafQBpHMg/ZGY9hcbnBVc5IPLtMb+Hy9x0z0=)
There still seems to be a problem when the parent uses a render function: - [Playground](https://deploy-preview-13396--vue-sfc-playground.netlify.app/#__SSR__eNp9Uk1rwzAM/SvGl7VQksN2KllhGz1ssA+2Hn0xidq6c2zjjy5Q+t8n20laSmkIWNJ7kp9kHeiTMcU+AJ3TytVWGL9gSrRGW0/edcPlynLlhBdakbXVLbkryot4TL9jakw7kC059uQBgi5BDax5kEhhihALqgE7mWYv+j5YRbaT7JLL+2dDXAUpR6dPjl9ffU6w5uMi0QbwmI1pPNDGvyrHdumMeldrtRabYue0wlmkqozWujVCgv00UYBjdD7cxyiXUv+9pZi3AXpBmLOF+vdKfOe6GGP0y4IDuwdGR8xzuwGf4eXPB3Roj2CrmyCRfQP8BqdliBoz7TmoBmWf8ZLa1/RAQm1Wbtl5wLn2TUWhaTSJzyg+28uN1k9y74uHYaQ4xSuLEffKQ2sk94CjJqRqxD4ZaJ7tFjcGuO0BhJzUnpQDsTwxc5EyV6nKs9r0+A9qf+k6) The original issue came from some code on Vue Land, which was using a...
It seems like we have a lot of these edge cases around `v-bind` shorthand. e.g. #12298 and #12828. I'm wondering whether we need a rethink. Would it be better to...
I'm not sure whether it would be considered a problem, but this change would also impact `$refs`.