As per comment #0 followed the same steps and unable to reproduce it on  version 66.0.3359.139 using Windows 10. Attaching screencast for reference.

@Reporter: As we are unable to reproduce the issue from our end. Can you please let us know if we miss anything and could you please provide any test file/Screencast for better triaging this issue.

Thanks! 

Deleted: 840080.mp4 4.3 MB

	840080.mp4 4.3 MB View Download

Hi. Thank you for looking into this issue. I found it is not 100% repro. This is what I see on my end (about 50% times):

https://youtu.be/tAPP7PeV_CA

Please notice that cookies were deleted, but "File system" was still there.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

rkiryanov@ Thanks for the update.

Retried the issue on Windows 10 on the reported version 66.0.3359.139 and the latest Canary 68.0.3433.0 as per comment #3 and unable to reproduce the issue.

After enabling the  "Keep local data only until you quit your browser" option -> navigated to a site -> Exited and relaunched chrome, cannot observe the cookies of the previous session.
Attached is the screen cast of the steps followed.

As per comment #3. as the reporter has confirmed that the issue is inconsistent, requesting UI>Browser>Sessions team to look into the issue and help in further triaging.

Thanks..

Deleted: 840080.mp4 3.3 MB

	840080.mp4 3.3 MB View Download

If you look at the video I uploaded, reddit.com looked differently from your video (my has a large box over small topics). I noticed, the issue does not repro if reddit looks like on your video - no box in from and large topics.

I found tripadvisor.com reproduced this issue twice out of two times for me.

As per comment #6 tested this issue and we are able to reproduce the issue on reported chrome version 66.0.3359.139 and on latest chrome 68.0.3438.0 using Windows 10, Mac 10.13.3 and Ubuntu 14.04.  
 
Same behavior is seen on M62(62.0.3202.97) hence considering it as non-regression and marking it as Untriaged.
Thanks! 

I'm able to reproduce this with tripadvisor.com even without any extension. 
Using Clear Browsing Data for "Last hour" also leaves the file system entry behind. It looks like this entry doesn't actually contain any data but it should still be cleaned up properly.

As a very simple reproduction case:
1. Visit example.com
2. Execute "window.webkitRequestFileSystem(TEMPORARY, 1024, console.log)" in the console
3. Delete cookies for "Last hour" at chrome://settings/clearBrowserData
4. Check chrome://settings/siteData
5. See that example.com is still listed for file system storage.

Deletion for "All time" works correctly. 
nhiroki@, could you or some other file system owner take a look?

We need to own this on the storage team. (Not that I'd turn down Hiroki-san's help!) 

pwnall@ - can we prioritize appropriately?

I see two issues discussed in this bug.

1) The early comments state that some storage features don't honor the "Keep local data only until you quit your browser" preference. This is a fairly straightforward privacy bug and we can prioritize it accordingly.

2) Comments #8 and #9 state that storage features don't honor "Delete cookies for last X [hour / 24 hours / 7 days / 4 weeks / all time]". This is a bit unclear to me. Is the feature supposed to be a rewind (set the local state to what it was X ago) or a selective nuke (delete the local data for every site I've accessed in the last X).

This matters because selecting nuking is possible, but I don't know how to implement rewinding efficiently (without burning through disk space) for most of our storage mechanisms. Even if disk space weren't a concern, rewind would have to be implemented feature-by-feature in AppCache, Cache Storage, DOM Storage, FileSystem, IndexedDB, and WebSQL. This would be a multi-quarter project.

dullwebber@: Would it make sense to focus this bug on the first issue (per the title) and move the 2nd issue into a separate bug, where we discuss what's the meaning of the feature and what guarantees we can provide for it?

Removed Target-68, because I'm fairly sure we wouldn't pursue a merge for this.

Sure, the first part is more important. I assumed that it is the same issue because the remaining data looks similar and both are partial deletions. 

Delete for the last hour remvoves all data that was modified during the last hour. 

I can reproduce this issue on Chrome 69. Local storage as well as indexedDB data are preserved after session.

No repro for me for comment #9 on tip-of-tree.

Issues with "Keep local data only until you quit your browser" appears to be a duplicate of  issue 791231  so resolving this. If there's a separate repro, let's get a different bug.