Topic "Scrolling": separate and enhance with common practices
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 74
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
The topic Scrolling is currently a child topic of sap.m. However, scrolling does not apply only to sap.m controls but also to other control libs such as the sap.uxap (e.g. .ObjectPageLayout) and sap.f (e.g. .DynamicPage). I guess the "Scrolling" page was created before the sap.f library was even introduced.
It would be great if there is a separate, up-to-date, and sap.m-agnostic "Scrolling" topic and subtopics that cover, in addition to the current existing content, also scrolling related practices for application developers such as:
- Keeping the container header pinned/sticky/stable, for example, wrt tables and icon tab controls:
- Programmatically scrolling to a specific section of the page, depending on which container or layout control is used (
sap.m.Page,sap.uxap.ObjectPageLayout,sap.f.DynamicPage, etc.). Programmatically scrolling inObjectPageLayoutespecially comes with a caveat as discussed in "ThescrollToSectionmethod does not scroll" - Stack Overflow and https://github.com/UI5/openui5/issues/2408.
This would improve the discoverability of the above control behaviors that are commonly asked in the community.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/08_More_About_Controls/scrolling-66029f6.md and its parent sap-m-48d9390.md, then review the linked examples for sap.m, sap.uxap.ObjectPageLayout, and sap.f.DynamicPage. Separate the topic from sap.m and document common sticky-header and programmatic-scrolling practices, including the ObjectPageLayout caveat. Done means the guidance is current, discoverable, and applies across the named containers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100