Skip to content

Is this a bug? After calling effectScope.stop(). The component render function outside the scope will not update anymore. #14357

@tianjian-sky

Description

@tianjian-sky

Vue version

=3.5.17

Link to minimal reproduction

https://play.vuejs.org/#eNqdVM1u00AQfpXRXuKqrtNSEFJIKyj0AAeKaMWFRch1Jq7bza61P2mkKBKIExISL4CEuMCRMwfeBlB5C2Z369ZJoxzwwfHOfLPzzbffZsoe1HU2dsh6rG8KXdUWDFpX73JZjWqlLUxB4xBmMNRqBB2Cdtopk8JJLgcC97CsZLPYn1S2KeEs62qTWcPZPS65LJQ0Fo49HHYgWYOdXZhyCe19kjUuZw0U5WAZ0PeYw+WDBRx1HefCYWZsXuL6esD2u3FMGpAWFke1yC3SCiDAetMp1YXPGcEB+sfOWiXhfiGq4myHs0Cds93w2+/GdNjgBpSoE5Deq2HEnGD0noN5ri1+LGXW0KTDqsxOjZJ0YmFKzgo1qiuB+qC2FSnBWS/O73O5EOr8SYhZ7TBt4sUJFmdL4qdm4mOcPdNoUI+Rs6uczXWJNqb3D5/ihL6vkiM1cILQK5LP0SjhPMcI23P+HHULF9g+DuaqZHlk9icWpWmG8kQ9chbwnJEXH64Y/ZrudnY71JEBSMVgRlKv7e8UcDjEwh4WqsYUznNbnCx4nkuchILoNm3IbFSZhH7ROrAZmNEp1bSQTgjqSBZdKG0Zfd6wMU17WRd2v/TvZQMKRl9Sagu6Xeq2ld5Kt9MwXAPwvQnQGsdfkvl8pp1MWn39E0ZOXsZou9urFJJAg666EoMX4XO+1j+euxKYCVUmnY0NIt9JIdaF/v7xWsQ3HcVSUcIfx39qsnlDk1gbJgtKEKgtwxLZ4plRGO1RNULl7KJO1RCS6x3XyD7UNfolag6/fnz+/fH7xbuffz+9ufj69s/7bxdfPsDRwaODXluwAR67siT7t2LXG9NUqo4nF5SLvofNRjvy8esxan83yMrb2Z1s6y6b/QOI6+2I

Steps to reproduce

  1. click begin button. The ui show the initial ref value 1000. And in the programme I created an effectScope and a watch funcion inside it watching the change of this ref.
  2. clck add button. The ref value was added by 1. The ui show the updated value 1001 correctly.
  3. click end button. This will call effectScope.stop(). And reset the ref value to 0. The ui show the value 0 correctly.
  4. click begin button again. The ui always show 0 and does not update anymore, though the ref value is changing.

What is expected?

After step 3 and step 4, the ui shows the correct ref value, and keep updated with it's changing.

What is actually happening?

After step 3 and 4. The ui shows 0 and does not update anymore

System Info

vue >= 3.5.17

Any additional comments?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔨 p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.has workaroundA workaround has been found to avoid the problemscope: reactivity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions