You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently in process of creating the demo app with UI5 Angular WebComponents, which includes the concept of "draft handling" - ability to store the current working state of the object in so-called "draft" table in the database. That implies that after user changes some field on frontend the request should be immediately fired to backend and new (updated) state shown to user.
That worked quite smooth with WC on Angular until we reached the point when the page was big enought to enable scrolling. Then after each request it starts to scroll the whole page to the top, which looks quite weird. The quick googling results to the router property of Angular called scrollPositionRestoration, which is enabled in our case, but not working unfortunately. Further googling shows that there are some problems and open issue with this property, which is still not solved :(
Therefore the question would be: do you have maybe in the framework some workaround of that behaviour - some page/router attribute/setting which could help to solve the problem?
Thank you in advance!
Expected Behavior
Keep the scroll position after request
Context
UI5 Web Components version: {1.1.2}
OS/Platform: {macOS 12.2.1 (21D62}
Browser: {Chrome Version 98.0.4758.109 (Official Build) (x86_64)}
Priority
Low
Medium
High
Very High
Stakeholder Info (if applicable)
Organization: {SAP}
Business impact: PoC
The text was updated successfully, but these errors were encountered:
The scrolling problem described is Angular Router related, and not reproducible using only UI5 Web Components.
Perhaps @SAP/ui5-webcomponents-core may have a suggestion for a possible workaround.
As routing is out of our scope, I'm closing this issue.
Bug Description
Hi colleagues!
We're currently in process of creating the demo app with UI5 Angular WebComponents, which includes the concept of "draft handling" - ability to store the current working state of the object in so-called "draft" table in the database. That implies that after user changes some field on frontend the request should be immediately fired to backend and new (updated) state shown to user.
That worked quite smooth with WC on Angular until we reached the point when the page was big enought to enable scrolling. Then after each request it starts to scroll the whole page to the top, which looks quite weird. The quick googling results to the router property of Angular called
scrollPositionRestoration
, which is enabled in our case, but not working unfortunately. Further googling shows that there are some problems and open issue with this property, which is still not solved :(Therefore the question would be: do you have maybe in the framework some workaround of that behaviour - some page/router attribute/setting which could help to solve the problem?
Thank you in advance!
Expected Behavior
Keep the scroll position after request
Context
Priority
Stakeholder Info (if applicable)
The text was updated successfully, but these errors were encountered: