Recently, I have encountered an issue with demux visualizations. Interactive quality details are just collapsing and one can see only the narrow area that can be scrolled on the right side. I just ran 5 batches, with 4 of them having exactly this issue. Decided to report here as a bug.
Tested on Ubuntu 24.04, with qiime2-amplicon-2025.10, and 2025.4.
UPDATE1:
Issue can be reproduced with Chrome, but Firefox works with no issues.
I notice there's a scrollbar of an absurdly familiar height of 300px in your screenshot. Suggesting that the logic we use to expand an iframe isn't working anymore on the old tabbed templates.
Do you see the same issue with feature table summaries? I'm expecting basically the same thing to happen there.
I don't seem to be able to reproduce this, I have tested the above r5-demux.qzv files on these systems:
OS X (M3): Chrome Version 142.0.7444.176 (Official Build) (arm64)
Linux (Ubuntu 24.04.2 LTS x86): Chrome Version 142.0.7444.175 (Official Build) (64-bit)
Long shot, but I think those errors are actually from an ANCOMBC2 Visualization.
Is there any chance you have some of them open at the same time while you are loading these visualizations? I wonder if the service worker is attempting to fetch a URL each time a new Viz loads, and the 404 takes long enough that it times out on the iframe measurement.
Each 404 seems to happen under the same "session id" so that's why I think it might be unrelated visualizations causing this.
I had it open previously today, but they were closed by the time of the test.
What I did after closing all other tabs:
Updated Chrome to the latest version
Cleared history/cashe
Restarted my PC
Just checked again and was able to reproduce the issue. I also remember having the same issue with the same batches but analysed with 2025.4 version of q2. Issue was repeated on laptop and PC, with the same version of Ubuntu, but different versions of Chrome. With Firefox, it works well on both.
Logs were shortened after updating and clearing the history, but didn’t change after unregistering the worker.
But thank you for your test with Linux + Chrome and not confirming the issue. Previously, I was blaming Chrome (since there were no issues in Firefox), but after your feedback, I tested it in “Incognito” mode. No issues were detected, so I went back to the usual mode and disabled all extensions one by one. After disabling Grammarly, the issue disappeared.
Thank you again for your time and help! I should have thought about “Incognito“ mode earlier.