Skip to content
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

Blurring an empty TextField (without doing anything in the field) causes a server visit #17429

Closed
mstahv opened this issue Aug 11, 2023 · 5 comments

Comments

@mstahv
Copy link
Member

mstahv commented Aug 11, 2023

Description of the bug

Blurring an empty TextField (without doing anything in the field) causes a server visit

Expected behavior

There should be no obsolete server visits.

Minimal reproducible example

Use this UI, click text field and document body repeatedly, watch the show in web inspectors network tab.

@Route
public class MainView extends VerticalLayout {

    public MainView() {
        TextField textField = new TextField();
        add(textField);
    }
}

Versions

Vaadin: 24.1.4
Flow: 24.1.5
Java: Eclipse Adoptium 17.0.2
OS: aarch64 Mac OS X 13.5
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
Live reload: Java active (Spring Boot Devtools): Front end active

@knoobie
Copy link
Contributor

knoobie commented Aug 11, 2023

Doesn't the dirty flag already fixes this? Or does this still happen with the new flag? vaadin/web-components#6160

Edit: more information about the flag here: vaadin/flow-components#5712 which describes exactly your problem that leaving the field causes a server rountrip with no change

@TatuLund
Copy link
Contributor

Related to vaadin/flow-components#4986

@caalador
Copy link
Contributor

As the event is a validated event let's see what happens after the components validation logic update.

@vursen
Copy link
Contributor

vursen commented Nov 6, 2023

The issue will be resolved as part of vaadin/flow-components#5537.

@yuriy-fix
Copy link
Contributor

The issue is resolved as a part of #5537. Fix is available in 24.3.0-beta1.
DateTimePicker behaviour will be tackled separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

7 participants