Git Product home page Git Product logo

Comments (7)

antifuchs avatar antifuchs commented on July 21, 2024

Update: Extracting the autofocus form component into a separate component does the trick:

#[derive(Properties, PartialEq)]
struct TitleInputProps {
    onchange: Callback<String>,
    value: String,
}

// Workaround for https://github.com/patternfly-yew/patternfly-yew/issues/145:
#[function_component(TitleInput)]
fn title_input(TitleInputProps { onchange, value }: &TitleInputProps) -> Html {
    html! {
        <FormGroup required=true label="Title">
            <TextInput required=true autofocus=true {onchange} value={value.clone()} />
        </FormGroup>
    }
}

This allows me to put a validation on the field too, without as much clutter, but it still feels weird.

from patternfly-yew.

ctron avatar ctron commented on July 21, 2024

There might be an issue with the initialization of the "focus" part. Re-rendering might cause that to be re-executed. Although I haven't experienced that myself.

from patternfly-yew.

antifuchs avatar antifuchs commented on July 21, 2024

Hm, I notice that the input_ref on TextInput has a #[prop_or_default] annotation, and I'm not passing a r#ref into the component... could it be that when the containing component re-renders, the node reference gets re-set due to the default call, which changes the input_ref value into something non-equal, which re-triggers the effect in this line?

from patternfly-yew.

antifuchs avatar antifuchs commented on July 21, 2024

...aaand confirmed, this goes away when I set r#ref={node_ref} (using a thing I created with use_node_ref() as normal), the issue goes away. I think it might be dangerous to use Default::default() with NodeRefs?

from patternfly-yew.

ctron avatar ctron commented on July 21, 2024

I think it might be dangerous to use Default::default() with NodeRefs?

Maybe :) … Can you come up with a PR?

from patternfly-yew.

antifuchs avatar antifuchs commented on July 21, 2024

I think I have an idea how to fix this - we can use use_effect_with((), move ...), which should run only on first render. Or use the autofocus prop as the criteria for when to re-run. I'll experiment and send something!

from patternfly-yew.

antifuchs avatar antifuchs commented on July 21, 2024

That was easy! #147 (:

from patternfly-yew.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.