Add a Not for Navigation disclaimer - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new "Not for Navigation" disclaimer dialog to the application, making it clear to users that the app is for informational use only and should not be used for operational flight planning or navigation. The dialog provides details about data sources and known differences from official publications, and is accessible from the top bar. The implementation includes both the new React component and its associated styles.
New "Not for Navigation" disclaimer dialog:
NotForNavigationReact component, which displays a modal dialog explaining the app's limitations, data sources, and known deviations from official sources. The dialog is accessible via a button in the top bar, uses a portal for rendering, and includes accessibility features such as keyboard handling and focus management.NotForNavigation.module.cssfor dialog layout and responsive design, ensuring the disclaimer is visually clear and mobile-friendly.Integration into the layout:
NotForNavigationcomponent in theTopBar, making the disclaimer accessible from every page. [1] [2]