You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide the following version numbers that your issue occurs with:
CLI: 3.4.1
Cross-platform modules: 4.0.0
Please tell us how to recreate the issue in as much detail as possible.
Second tabItem title is not measured/arranged properly and gets wrapped in a scenario with opening a modal dialog with root tabview visual inside. Note that the problem is only present if the modal dialog is opened with fullscreen flag set to false.
See the attached screenshot (can be reproduced in e2e/modal-navigation):
The text was updated successfully, but these errors were encountered:
manoldonev
changed the title
Tabitem title not measured/arranged properly in a modal dialog with root tabview inside
[TabView] Tabitem title not measured/arranged properly in a modal dialog with root tabview inside
Feb 19, 2018
…5392 (#5435)
BREAKING CHANGE: [Android] NativeScript no longer overwrites the horizontal/vertical alignment on the user-defined root visual element when opening it in modal dialog window (i.e. not fullscreen).
If your application logic relied on the previous behavior you need to manually set `horizontalAlignment="center"` and `verticalAlignment="middle"` on the root visual element you are showing modally.
Uh oh!
There was an error while loading. Please reload this page.
Which platform(s) does your issue occur on?
Android
Please provide the following version numbers that your issue occurs with:
Please tell us how to recreate the issue in as much detail as possible.
Second tabItem title is not measured/arranged properly and gets wrapped in a scenario with opening a modal dialog with root tabview visual inside. Note that the problem is only present if the modal dialog is opened with fullscreen flag set to false.
See the attached screenshot (can be reproduced in e2e/modal-navigation):
The text was updated successfully, but these errors were encountered: