Skip to content

Vaadin Multiplatform Runtime 5.0.4

Choose a tag to compare

View all tags
@mshabarov mshabarov released this 25 Aug 09:14
5.0.4
95c3aed
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Vaadin Multiplatform Runtime 5.0.4

The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 20+ (Flow) applications.

The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.

The complete documentation can be found here

Fixes since the 5.0.3 Release

  • Unlock after session access.
  • Report a possible reason of FW UI absence in RPC handling (Issue: #80).
  • LegacyComponent should handle enabled change (Issue: #82).
    A LegacyComponent should set the framework component to the correct enabled state if the wrapper state changes due to a parent component being disabled/enabled.
  • Hide tooltip on mouse out event (Issue: #89).
    Adds a tooltip mouse move handler to the root panel to ensure a tooltip is being hidden properly.
  • Message processing to be after initial UIDL (Issue: #86)
    This delays the purging of the pending response queue until the initial UIDL is being processed and makes sure everything from the initial UIDL is processed by using a deferred command to purge the queue.
  • Allow MprNavigator deal with SingleComponentContainer (Issue: #36).
  • Store navigator created using a component in a field (Issue: #39).
  • Set up response handler if wrapper element is hidden (Issue: #91).
  • Clean up legacy UI and content on session destroy and UI detach.
    Adds session destroy listener to clean up legacy session and detach listener to remove legacy UI from session to avoid potential memory leaks: legacy UI holds reference to Flow UI. Removes MprUIContent from session when detached. MprUIContent holds Flow UI reference, thus possible memory leak preventing Flow UI's getting GC'd.
Assets 2
Loading