...
When collapsed threads is enabled, notifications behave differently - see matrix of scenarios and associated outputs here (full spreadsheet of the chart below)
Client Terminology:
CRT Unsupported Client = client doesn't have the CRT front end code (CRT supported flag = false by default). This includes,
Old mobile versions that don’t have the CRT code yet
Webapp/server versions that don’t have the CRT front end available to enable yet
CRT Supported Client = client has the CRT front end code (Client sends CRT supported flag = true). This includes,
New mobile versions that have the CRT code
New webapp/server versions that have the CRT front end available to enable in config settings
CRT Off Client = client is CRT supported but the user has the feature off. This includes when the,
Admin has the CRT config setting “off”, or
User has feature turned off in account settings
CRT On Client = client is CRT supported and the user has the feature on. This only occurs when the user has CRT enabled in account settings.
...
Desktop Notifications
When a user receives notifications about a root post - no change to existing flow. Take the user to the channel, scrolled to the root post
When a user receives notifications about a reply post in a thread that is followed, take the user to the thread in the Global Threads context
When a user receives notifications about a reply post in a thread that is not followed, take the user to the thread in the Channel context (RHS)
...