From 30a14c568764b2e233ba04e615e842ae31c739b7 Mon Sep 17 00:00:00 2001
From: Dannon Baker <dannon.baker@gmail.com>
Date: Tue, 3 Mar 2026 21:23:06 -0500
Subject: [PATCH] Fix HTML dataset extra files 404 in preview

The switch from srcdoc to iframe src (d3b31b05540) broke HTML datasets
that reference extra files via relative paths (JBrowse2, FastQC, etc).
Without a trailing slash on the display URL, the browser resolves
relative paths against /datasets/{id}/ instead of /datasets/{id}/display/,
so sub-resources like static/js/main.js hit routes that don't exist.
Adding the trailing slash fixes resolution and matches the existing
pattern in HistoryDatasetDisplay.vue.
---
 client/src/components/Dataset/DatasetDisplay.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/client/src/components/Dataset/DatasetDisplay.vue b/client/src/components/Dataset/DatasetDisplay.vue
index 804ee8263d2..566b2562459 100644
--- a/client/src/components/Dataset/DatasetDisplay.vue
+++ b/client/src/components/Dataset/DatasetDisplay.vue
@@ -37,7 +37,7 @@ const sanitizedToolId = ref<string | null>(null);
 const { isAdmin } = storeToRefs(useUserStore());
 
 const dataset = computed(() => getDataset(props.datasetId));
-const datasetUrl = computed(() => `/datasets/${props.datasetId}/display`);
+const datasetUrl = computed(() => `/datasets/${props.datasetId}/display/`);
 const downloadUrl = computed(() => withPrefix(`${datasetUrl.value}?to_ext=${dataset.value?.file_ext}`));
 const isLoading = computed(() => isLoadingDataset(props.datasetId));
 const previewUrl = computed(() => `${datasetUrl.value}?preview=True`);