-
Notifications
You must be signed in to change notification settings - Fork 14
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
Поведение телепортов при деактивации родительского компонента #1275
Comments
shining-mind
changed the title
Поведение телепортов при деактивации страницы
Поведение телепортов при деактивации родительского компонента
May 21, 2024
shining-mind
added a commit
that referenced
this issue
Jul 26, 2024
* fix #1275 * chore: stylish fixes * chore: fixed naming * fix: fixes after refactoring * chore: added new tests * Sync test for teleports (#1356) * tests(p-v4-components-demo): accept search param for goto * chore(i-static-page): remove console.log * fix(core/component/watch): fix flush post watchers * tests(i-block): fix sync className test for teleport --------- Co-authored-by: kobezzza <kobezzza@gmail.com> Co-authored-by: Artem Shinkaruk <46344555+shining-mind@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Текущее поведение:
Устраивает ли текущее поведение? Или надо сделать иначе, например: компонент должен деактивироваться и удаляться из DOM, а при активации добавляться в DOM вручную.
The text was updated successfully, but these errors were encountered: