-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
ref(layout): use Layout.Page on isolated pages #111644
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
Merged
priscilawebdev
merged 9 commits into
master
from
JonasBa/ref/layout-page-isolated-pages
Mar 27, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
bb00c17
ref(layout): use Layout.Page on isolated pages
JonasBa 1b29093
fix(layout): move Layout.Page to conversations layout
priscilawebdev 77fa247
fix(layout): move Layout.Page to profiling container
priscilawebdev 7416527
fix(layout): revert profiling container approach
priscilawebdev 4fe24a1
fix(layout): move Layout.Page to profiling providers
priscilawebdev d81284e
fix(layout): use LayoutPageWithHiddenFooter in profile summary
priscilawebdev 1af0357
fix(layout): use LayoutPageWithHiddenFooter in differential flamegraph
priscilawebdev e398f48
ref(profiling): extract shared LayoutPageWithHiddenFooter
priscilawebdev 0bafba0
ref(profiling): move LayoutPageWithHiddenFooter to own file
priscilawebdev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| import styled from '@emotion/styled'; | ||
|
|
||
| import * as Layout from 'sentry/components/layouts/thirds'; | ||
|
|
||
| // The footer component is a sibling of this div. | ||
| // Remove it so the flamegraph can take up the | ||
| // entire screen. | ||
| export const LayoutPageWithHiddenFooter = styled(Layout.Page)` | ||
| ~ footer { | ||
| display: none; | ||
| } | ||
| `; |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Layout wrapper at wrong level causes nested main elements
Medium Severity
Layout.Pageis added toConversationsLayout, which wraps all child routes viaOutlet— includingtransactionSummaryRouteandtraceView, both of which render their ownLayout.Page. This creates nested<main>elements (semantically invalid HTML) and breaks the~ footer { display: none; }CSS sibling selector ontraceView's innerLayoutPageWithHiddenFooter, since the footer is now a sibling of the outer<main>only. The PR description indicates the fix belongs inoverview.tsx, notlayout.tsx.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a bug. The conversations page renders a table and drawer. transactionSummaryRoute and traceView are included as children following the same pattern as all other insight pages (frontend, backend, mobile, etc.). No visual or functional issue observed.