Problem

Updates to signals in children seems to cause the parent to re-mount triggering the onmounted event to re-occur even though it should already be in the DOM.

This seems to be caused by #3271, reverting to a previous commit does not show this behavior.

I was trying to implement a virtual scroll element and my scroll container was being remounted continuously, it had been working in prior 0.6 alphas. Extracting the child elements and the counter into their own component does resolve the issue in simple components, but doesn't in more complex cases.

Steps To Reproduce

Steps to reproduce the behavior:

use dioxus::prelude::*;

fn main() {
    dioxus::launch(App);
}

#[component]
fn App() -> Element {
    let mut counter = use_signal(|| 0);
    let mut saved_element = use_signal(|| None);
    rsx! {
        div {
            onmounted: move |element: Event<MountedData>| {
                println!("MOUNTING");
                saved_element.set(Some(element.data()));
            },
            button {
                onclick: move |_| {
                    *counter.write() += 1;
                },
                "INCREMENT"
            }
            div { "{counter}" }
        }
    }
}

The same issue can be seen on your read_size example if you add logging to the mount event:
https://github.com/DioxusLabs/dioxus/blob/main/examples/read_size.rs

Expected behavior

The parent should be mounted once and stay mounted, only its children should update when a relevant signal is written to.

Screenshots

Environment:

• Dioxus version: 0.6.0
• Rust version: 1.83.0
• OS info: Windows 11
• App platform: Desktop

Questionnaire