Problem
When a user reports a long Search/Reports loading skeleton, the existing [Search] Showing skeleton log fires the moment the skeleton appears and does not capture which of the many interdependent conditions is still holding it (data not loaded, search still loading, errors, card feeds loading, heavy-work defer, etc.). That makes it hard to diagnose slow-load repros without guessing.
Solution
Add a diagnostic hook, useStuckSkeletonLog, that logs a one-off snapshot of all skeleton conditions if the skeleton stays visible past 5 seconds. This is diagnostic only and changes no rendering or behavior, so the next slow-load repro shows exactly which condition is stuck for that user.
PR
#94697
Issue Owner
Current Issue Owner: @BartekObudzinski
Problem
When a user reports a long Search/Reports loading skeleton, the existing
[Search] Showing skeletonlog fires the moment the skeleton appears and does not capture which of the many interdependent conditions is still holding it (data not loaded, search still loading, errors, card feeds loading, heavy-work defer, etc.). That makes it hard to diagnose slow-load repros without guessing.Solution
Add a diagnostic hook,
useStuckSkeletonLog, that logs a one-off snapshot of all skeleton conditions if the skeleton stays visible past 5 seconds. This is diagnostic only and changes no rendering or behavior, so the next slow-load repro shows exactly which condition is stuck for that user.PR
#94697
Issue Owner
Current Issue Owner: @BartekObudzinski