-
Notifications
You must be signed in to change notification settings - Fork 536
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
fix(PageLayout): restore main landmark #3737
Conversation
🦋 Changeset detectedLatest commit: 245b067 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
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.
Oof tough spot! But really good rollout plan!
(not for this PR, but for after) How do you feel about this slight change: Right now, the default element is How do you feel about supporting the So, changing the default from |
@siddharthkp I like it, works for me! |
Follow-up to: #3675
Currently, we have teams in a couple of situations where either:
main
landmark and therefore runs into the duplicate landmark violationmain
landmark fromPageLayout.Content
When removing the
main
landmark, teams in the latter group are impacted. In this PR, we introduce anas
prop to allow for teams in the first example to change the semantics of this component toas="div"
as they already have amain
defined.Rollout
This is an incremental rollout strategy if our ideal here is to remove
main
as a landmark fromPageLayout.Content
. With this path, we could swap teams to useas="div"
before removing themain
support and also droppingas="div"