New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. #10813
Comments
Your reproduction doesn't show that error |
Looks like the problem is
in function patchAttr(el, key, value, isSVG, instance) {
if (isSVG && key.startsWith("xlink:")) {
if (value == null) {
el.removeAttributeNS(xlinkNS, key.slice(6, key.length));
} else {
el.setAttributeNS(xlinkNS, key, value);
}
} else {
const isBoolean = isSpecialBooleanAttr(key);
if (value == null || isBoolean && !includeBooleanAttr(value)) {
el.removeAttribute(key);
} else {
--> __el.setAttribute(key, isBoolean ? "" : value);__
}
}
} The problem was detected in v3.4.24. This was not the case in v3.4.23. |
Please provide a runnable reproduction |
Same error happens to me when updating from v3.4.23 to latest v3.4.26.
|
I am seeing the same failure. I don't (yet) have a simple reproduction case to share. |
This is my version "dependencies": { |
Same issues:
...followed by...
Code Snip...
Changing
to
just moves the error elsewhere and breaks overall theme changes (sub-components don't change as follows). In any event, theme changes are broken--the page does not update using the new theme name. Sub-components theme changes on a move to another component. The app works without issues using vue@3.4.23. A minimal viable example is not possible from this code base. As a follow up, I will incrementally test with later versions to hopefully narrow down the breaking change. |
The warnings and errors in #10813 (comment) are introduced in vue@3.4.24 While the example demonstrates the issue within Vuetify3 components, the Vue3 version packaged is the controlled change applied by Another observed problem (version above 3.4.23) is when moving the mouse between a VNavigationDrawer and a VMain holding a RouterView produces the following:
...and...
|
@nongtan7898's reproduction can't reproduce that error. |
I can't speak for the other folks, but updating to Vue v3.4.27 fixed this issue for me. |
Vue version
3.4.25
Link to minimal reproduction
https://play.vuejs.org/#eNqtVm2L00AQ/itLVGghxneFeginV0HxTjnrCxgpazJtVze7Ibu53nnchxNB/X4oviCoiKAIeqKk/yY/xdlN79qksSjYD2V3Zp5nXnZ2J5vOYhx7ayk4LWdBQxRzquHcwpH9pS98saCChMUa17Aey0STEHo05ZpsGi0hQ6qDQcvsCP66fdAXZIKGVDMp9uWEULUhAjKgIuSQNAQMb1KegkskD+2qOTElhPVIY8hEKIfewYbvHIg2OvQehylm32l6S1RTK280S2h0NqRMk39i8EJQOpEbjebZCdPWZPnvlKWIOBX9lPZhqiLFL4SARZS3iO/4jlvW4TnowolR56PHefYuHz01/9nPPPuQZ7t59j7Ptu0Ct4/y0bM8+2oNRnn2cYaRiZ4suBDzOc928uxJHdEL42D0lHSvdxZXO12SZ8/z7Bcak257ZcnsMQo03SbdztXO4hUjqbLUOm+blP5nNhcZ15BAaDgbFoxIxGBa4xBtNt8tFwq/WLod0l1evF0XdbPWyzWp9EW2XntKeiBThX2tjNadUXMQfT1YBpFWC4/XZbm9cuOvasclDZnor0Igk8KTtf2BZTHJYWajRzY53CJ3tXSe581QxokMQClkraPLXtuovlmKT1b+5g9ECmhi3gBD8tg6fmlD2W3NmD6ERE7nMGmCt3n2ak4nVphnk6F9JvDNmrlfhPRYonQRHUJfWppdew5Ivz3DZO5qjb05tMzW9sWe5H0NFl/JMRYvDBZyx6b4usYyTmCNYefsFd/kiAdWJDj2OgPbKu3Lu0DyNBJL0EPKO2XYJgkwKbVCI/uShPpwAAKvDfITTRN8tG0YXcq571Ro69D3ZLhxmENPlwjunHDJSZecdsmZuzUkQxZq2yXHjh4q44675NRcxPEqwniaizhVARx1ybH60O6WdjjtJOe3W0QnOJ1KMyXV8lZB36NclZUJqFgKxdawQhXk1mSgTByHAHHFkkURhMy28JS8gJh/nEULR8bD2HEdrQIpeqzv3VdS4AC3be87gYxihhP2amwGkvKd/QvhO3i6cnjZyqY8IGYAwYMa+X21bmS+cw3Tg2QN9tvRd4rKFur29RXs+illJMOUo/Uc5SoobNdiaBqz86n9MJiys9Feisw3Bz5RHdVe14AVHidlAt2rjLHGr5gLc1KfhHvCO2lxWFBn6zeuanY4
Steps to reproduce
What is expected?
Solved my problem.
What is actually happening?
runtime-core.esm-bundler.js:47 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://github.com/vuejs/core .
at
at <Establishment onVnodeUnmounted=fn ref=Ref< Proxy(Object) {__v_skip: true} > >
at
at <Dashboard onVnodeUnmounted=fn ref=Ref< Proxy(Object) {toggleAside: ƒ, …} > >
at
at
System Info
No response
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: