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
There are different issues with the history component:
The component does not update when the history changes - should be refactored to use an Observable
The cookie reading/writing is quite complication and is done multiple time while changing the history - rewrite to have a single entry point.
initializeCookieSettings is called every time a component is used (history and pinned history)
Make max entries, cookie names, max age configurable
Username should not be outside of the context, it should be just another context property. Maybe event better: flatten the context to a single string - the using party can concat this themselves.
Handle links and iOS app mode correctly, when single history-items are located in different tlds due to modularisation.
Ensure that we keep the following design goal intact:
we need to ensure proper link styling!
valid "a href" seems to be required for clarity to apply styling.
from ux-point of view we should enable the user to open a history-item in a new tab quickly
("CRTL+Click", "Left-Click > open in new Tab", ...)
App-Mode must be supported and UX must not be brocken on mobile devices.
this includes having different tld in history-items.
Nice to have:
if URL is in the current application's route then do not reload page but just open the route
The text was updated successfully, but these errors were encountered:
There are different issues with the history component:
initializeCookieSettings
is called every time a component is used (history and pinned history)Ensure that we keep the following design goal intact:
we need to ensure proper link styling!
valid "a href" seems to be required for clarity to apply styling.
from ux-point of view we should enable the user to open a history-item in a new tab quickly
("CRTL+Click", "Left-Click > open in new Tab", ...)
App-Mode must be supported and UX must not be brocken on mobile devices.
this includes having different tld in history-items.
Nice to have:
The text was updated successfully, but these errors were encountered: