fix(files_version): mtime confusion on milliseconds

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>

Author: blizzz

apps/files_versions/src/views/FilesVersionsSidebarTab.vue

@@ -73,7 +73,7 @@ const loading = ref(false)
 const showVersionLabelForm = ref(false)
 const editedVersion = ref<Version | null>(null)
 
-const currentVersionMtime = computed(() => props.node?.mtime?.getTime() ?? 0)
+const currentVersionMtime = computed(() => Math.floor(new Date(props.node?.mtime?.getTime() ?? 0).getTime() / 1000) * 1000)
 
 /**
  * Order versions by mtime.
@@ -130,6 +130,7 @@ const canCompare = computed(() => {
 // When either the current node to show or its mtime changes we need to refetch the versions
 // When the id changed we immediately show changes
 watch(() => props.node.id, loadVersions, { immediate: true })
+
 // On mtime changes we debounce to prevent too many requests.
 watchDebounced(currentVersionMtime, loadVersions, { debounce: 600 })
 
@@ -139,7 +140,10 @@ watchDebounced(currentVersionMtime, loadVersions, { debounce: 600 })
 async function loadVersions() {
 	try {
 		loading.value = true
-		versions.value = await fetchVersions(props.node)
+		// normalize the node`s mtime first – server does not report milliseconds, they are all 0
+		let normalizedNode = props.node
+		normalizedNode.mtime = new Date(Math.floor((props.node?.mtime?.getTime() ?? 0) / 1000) * 1000)
+		versions.value = await fetchVersions(normalizedNode)
 	} finally {
 		loading.value = false
 	}