Open antos-k opened 4 years ago
The Team in Munic is doing a big refactoring till end of September. this bug should be solved afterwards, because it might be solved during refactoring.
@antos-k could you show a screenshot for this bug?
this bug hasn't been solved yet.
I cant imagine how to work with that naming methodology.
Would you like to tell me, how can i work with elements?
But for now, i did that:
<NavButton
keyName = "save"
classname = "pure-u-1-2"
onClick = { () => {
this.props.handleSubmit();
document.getElementsByClassName('pure-form')[0].scrollIntoView({block: "start", behavior: "smooth"});
}}
icon = "save"
text = { t("save") }
/>
https://youtu.be/hZ4JUPD3Aoo Is that action what we looking for?
@k-gorod yes, you are in a right direction please make a pull request to understand your whole solution.
Im noticed that some of elements have names. I used it to check them values. PR created
@k-gorod дзякуй за ПР, у бліжэйшы час праглядзім
былі думы наконт таго, ці ёсць якая лібы для больш прыгожага рашэння, але акей, архітэктурна нейтральна там усё прымаю. будзем тэставаць)
Result: Form is not scrolled to top, so we can't see 'Something is missing, please check below.' message - user can to not understand, why nothing happens when he press Save. Expected result: Form is scrolled to the first validation message (so, user can see it and correct the reason)