Tips: status should be user-based not browser-based

[folletto]

While reviewing tips I was informed that to try a new one I had to clear my local data (related: #8051 about triggering it via URL). Which seems pointing out that the flags to trigger tips are local to the browser.

However, it doesn't make sense that a specific user have to get new tips every time they switch browser or device or profile. These kinds of informations are designed to be provided to each person once, and as such they shouldn't be repeated (unless requested by the user).

Suggestion:

• Store the tips "dismissed" status per-user

[afercia]

As far as I know, technically it's already stored on a per-user basis, but just in the browser's local storage :) It should be saved in the DB.

Worth noting many other preferences are stored just in the browser, for example:

• sidebar state
• sidebar panels toggled state
• fixed toolbar
• editor mode
• plugins pinned items
• etc.

That means the same user will see different UI settings when logging in with a different browser. So I guess the actual issue is a bit broader... 😉

[JJJ]

That means the same user will see different UI settings when logging in with a different browser. So I guess the actual issue is a bit broader

I agree. I expect all of those preferences to follow my account around, not my browser. These should be persistent to me, not the window I'm looking at at the time.

[aduth]

Thanks for the report. While I had created it after this one, the issue at #15105 contains the actionable technical implementation related to this task. I will close this to consolidate discussion.

See also: #19177

[aduth]

Duplicate of #15105