Skip to content

ObjectPage: Collection of known issues/limitations #248

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

Closed
3 tasks
clemai opened this issue Dec 11, 2019 · 0 comments · Fixed by #354
Closed
3 tasks

ObjectPage: Collection of known issues/limitations #248

clemai opened this issue Dec 11, 2019 · 0 comments · Fixed by #354
Assignees

Comments

@clemai
Copy link
Contributor

clemai commented Dec 11, 2019

List of issues with [Severity]

  • [MED]Wrong scroll position when item of IconTabBar is clicked. The scroll offset value has to be calculated, when the header is changing from expanded to collapsed state.
  • [LOW] Native scrollbar is still visible in some cases.
  • [LOW] The Title of the first SubSection don't hide if the first element inside the ObjectPage is not a SubSection (ObjectPage: first SubSection Title don't hide #25)

Reproduce 1

  1. ObjectPage with expanded header and default mode.
  2. Press item in the item tab bar in order to scroll to the selected section.

Reproduce 2

  • Scrolling with mouse near left border of scrollbar.
    Double scroll bars
@clemai clemai added the bug label Dec 11, 2019
@MarcusNotheis MarcusNotheis self-assigned this Mar 17, 2020
MarcusNotheis added a commit that referenced this issue Mar 19, 2020
This PR includes a full refactoring of the ObjectPage using native CSS capabilities instead of custom scroll handlers. This might lead to problems in IE11 and needs to be tested as well.

The Anchor Bar was replaced with the UI5 Web Component TabContainer in order to improve accessibility and RTL. --> #345

Closes #334
Closes #248
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants