Since clearHistory removes pages synchronously (but visits async), and visits addition is now async, if we quickly add a visit and immediately call clear history, it can end up being registered after clear history. This is rarely a problem in real usage since users are not so fast, but the issue is visible in tests. Similar issues could be visible with RemoveVisitsXXX and RemovePagesXXX APIs. We need either to find a way to kill related tasks in adding visits or to make all pages removals APIS async.
hm, where in the async api bug dependency tree should this be?
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.