github vaadin/flow 24.8.0.alpha2
Vaadin Flow 24.8.0.alpha2

latest releases: 24.7.0, 24.6.8, 24.5.16...
pre-release19 hours ago

Changes since 24.8.0.alpha1

All changes

New features

  • Add trees and transactions to signals module
    Commit · Pull request

    Still missing the topmost layer with the actual signal instances. The operation classes are leaking through from that layer even though they don't make much sense without the rest of that layer.

  • Add defaultAutoResponsiveFormLayout feature flag
    Commit · Pull request

    The PR introduces a new feature flag, defaultAutoResponsiveFormLayout, which enables auto-responsive mode for all form layouts by default. Part of vaadin/flow-components#7164

  • WebComponent more Jackson
    Commit · Pull request

    Change more parts of webComponent to use Jackson instead of elemental.

  • Use single scanner for plugin class scan
    Commit · Pull request · Issue

  • Router parts to jackson
    Commit · Pull request

    Use jackson for router and navigation.

  • Internals to jackson
    Commit · Pull request

    Change internal functions to use jackson. part of #20741

  • Jackson used in dev-server
    Commit · Pull request

    Use jackson instead of elemental in the dev-server. part of #20741

  • Add ignore version check to plugin params
    Commit · Pull request · Issue

  • Use jackson for setting up configuration
    Commit · Pull request

    Use jackson for setting up configuration settings. part of #20741

  • Change internal json handling to jackson
    Commit · Pull request

    Change internal json manipulation from elemental to jackson. part of #20741

  • Plugins to use jackson
    Commit · Pull request

    Update plugins to use jackson for json handling. part of #20741

Fixes

  • Ensure exported WebComponent adds absolute links to document.css
    Commit · Pull request · Issues 21120, 19620

    When using a development bundle, WebComponentBootstrapHandler adds a tag to the embedding document that references document.css for all used themes (application and parents). However, the URL is relative to the embedding document instead of being an absolute URL to the CSS resource. Additionally, the tag is added even if the theme does not provide a document.css file, potentially causing 404 errors at runtime. This change ensures that the link URL is calculated based on the request and that it only adds tags for existing CSS files.

  • Set page height to 100% instead of 100vh
    Commit · Pull request

    The PR modifies the page height from 100vh to 100% to prevent the content area from extending underneath the navbar on mobile devices: - body, #outlet { + html, body, #outlet { - height: 100vh; + height: 100%; width: 100%; margin: 0; }

  • Watch active project resources
    Commit · Pull request

  • Use add if not replacing
    Commit · Pull request

    Use add method if not replacing an old value.

  • Constant pool to jackson
    Commit · Pull request

    Use jackson in constant pool UidlWriter to handle response in jackson. Part of #20741

  • Prevent duplicated messages in client queue
    Commit · Pull request · Issue

    Messages sent by the Flow client are queued until the server acknowledges their reception. However, if there's a network fault, the Flow client immediately attempts to resend the message, resulting in duplicates in the queue. This change ensures that the same message is not added to the queue multiple times.

  • Fix equality check in NavigationAccessControl
    Commit · Pull request · Issue

  • Compute client-side feature flag values at runtime
    Commit · Pull request · Issue

    Activating a feature flag in the project does not work when a default bundle is used because the values of the flags sent to the client are hard-coded at bundle build time. Additionally, if a feature flag is active during bundle creation, it remains active on the client side even if the project does not activate it in the vaadin-featureflags.properties file. This change ensures that feature flags in the frontend bundle are always disabled initially and are activated on page load based on the current project settings.

Don't miss a new flow release

NewReleases is sending notifications on new releases.