-
Notifications
You must be signed in to change notification settings - Fork 27k
docs(docs-infra): move API members cards to the center of the page #58610
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
Conversation
|
Deployed adev-preview for 5ee82fd to: https://ng-dev-previews-fw--pr-angular-angular-58610-adev-prev-undk8pcw.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
067c28a to
e30de86
Compare
|
I'll revert the PR to a draft since I noticed that I've broken the CLI reference details until I issue a fix. |
149838e to
41b3257
Compare
4999cc8 to
1e4c039
Compare
1e4c039 to
e5fbe63
Compare
|
Got rid of it. |
JeanMeche
left a comment
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.
We probably should remove the click listener on the cards.
It us useless with the new layout
e5fbe63 to
a850dfa
Compare
|
Removed. The cards are still focusable but they no longer have listeners. Clicking on a code line and auto-scrolling to its card is still there. |
The problem is that this item and other items with class="cdk-visually-hidden" should be hidden.... we shouldn't remove these tags. This was fixed by #58812 |
|
I guess we need it for screen readers? I overlooked that. Will revert the change. Strangely, I was not able to reproduce the issue on |
a850dfa to
f7c2e7b
Compare
Exactly, Elements with these classes are intended for screen readers |
|
This PR is ready for review. |
|
The scrolling looks broken. If you click on |
|
If it's final that you will change the cards to be in the bottom permanently ... I believe we will have the opportunity to remove all the resize observer stuff and start using the straight forward scrollIntoView way It will add extra effort to change though but will save too much operations and we will get better performance What do you think? |
I am unable to reproduce it. Tried that on Chrome, Safari and Firefox. However, it seems that on my local setup I've closed the small "The state of JS survey" banner which is indeed covering the header section of the card when I tested the app from the demo link where the banner hasn't been closed yet:
Maybe this is what you are experiencing? I can add some margin so the scroll stops above the target element.
I initially planned this as "as small as possible change". I agree that upon further look there is some redundant code which is no longer used and can be removed. And this is actually done in the upcoming PR which is an evolution of this one where the tabs are removed, the template of the API details page is pretty much reduced to a single |
2492758 to
4c48f66
Compare
|
You're right the demo doesn't exihibit the issue anymore. Maybe I was hitting the cache. |
|
@JeanMeche, I updated the scroll margin top functionality to include @Ahmed-Hakeem, given the margin top was related in some way to the The change can be inspected in the last commit. I intentionally didn't squash it. Let me know, if there is anything else. If the PR is good to go, I will proceed with the squashing. |
4c48f66 to
1cf9ddf
Compare
…the page Move the members description section below the main content of the page since it is part of the core information about a doc item. The CLI reference details page is affected as well.
1cf9ddf to
5ee82fd
Compare
|
This PR was merged into the repository by commit 922ffdb. The changes were merged into the following branches: main, 19.0.x |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…the page (angular#58610) Move the members description section below the main content of the page since it is part of the core information about a doc item. The CLI reference details page is affected as well. PR Close angular#58610





PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The API members cards are rendered on the right-hand side of the main page content.

What is the new behavior?
The members cards are moved below the header, i.e. they are now part of the main page content in the center. This should improve the UX by effectively using the available free space on the page and emphasizing the importance of the members descriptions.

Does this PR introduce a breaking change?