Navigating back up the tree doesn't reload CIDs

[jessmartin]

Summary

Problem

When navigating around Drive, if the directory's contents are already loaded and you navigate back to that directory after the directory's contents have changed, the CIDs for the content are out-of-date.

Impact

When using Drive to grab CIDs by right-clicking "Copy CID" on the item, the CID is incorrect. Furthermore, because CIDs aren't human-readable, it's virtually impossible to tell that a CID is incorrect.

Solution

I would think we'd want to check for a newer CID every time we navigate to a directory.

Detail

Describe the bug
When navigating around Drive, if the directory's contents are already loaded and you navigate back to that directory after the directory's contents have changed, the CIDs for the content are out-of-date.

To Reproduce
Steps to reproduce the behavior:

1. Open any directory in Drive, which will call the "parent" directory.
2. Navigate to a directory within the parent directory.
3. Change a file in the parent directory.
4. Navigate back to the parent directory.
5. Right-click on the changed file and click "Copy CID."
6. The CID will represent the older copy of the file.

Expected behavior
The CID should be for the newly-edited file.

There could be further ramifications of this. Will new files show up?

Desktop:

• OS: macOS
• Browser: Chrome
• Version 102.0.5005.61