webrecorder
feat: Show all crawl runs + crawl deletion UX improvements
Resolves https://github.com/webrecorder/browsertrix/issues/2906
Changes
Overall, a more consistent experience for navigating all workflow crawls and managing crawl-related items.
- Adds new "Crawl Runs" page under "Crawling" to display all crawl runs, including canceled and failed
- Enables sorting crawls for by execution time and page count
- Updates icon for "Canceled" state to not appear as error
- Update archived item type labels
- Refactors archived item and crawl deletion confirmation to use same dialog (partially addresses https://github.com/webrecorder/browsertrix/issues/619)
- Show collections in deletion confirmation
- Refactors
/archived-items/crawl-list.tscomponent to ->/crawls/crawl-list/components
Manual testing
Note: New sort fields require building the backend locally.
- Log in as crawler
- Go to "Crawling". Verify "Workflows" and "Crawl Runs" tabs are shown
- Go to "Crawl Runs"
- Interact with search, sort, and filters. Verify list controls work as expected.
- Choose canceled crawl run. Verify navigation to crawl details view
- Choose action menu -> "Delete Crawl". Verify that crawl is deleted without confirmation
- Go back to "Crawl Runs"
- Choose successful crawl.
- Choose action menu -> "Delete Crawl". Verify that confirmation is shown.
- Repeat 9 from "Workflow" > "Crawls" and "Archived Items". Verify confirmation dialog is consistent for all crawl/item deletions.
Screenshots
| Page | Image/video |
|---|---|
| Crawl Runs | |
| Crawl Runs | |
| Workflow / Crawls | |
| Archived Items | |
| Delete Confirmation (when in collections) |
Follow-ups
A tag filter can be added once https://github.com/webrecorder/browsertrix/pull/2923 is merged.
Overall looks great! The one thing I've noticed is that the crawl runs table (and archived items table, as it appears to be the same component) doesn't adjust to smaller screen sizes as well as some of our other tables. Instead of responsively changing shape to fit the screen, some of the columns begin to get cut off. For instance:
Larger screen size
Medium screen size
Small screen size
We could address the responsiveness separately, I leave that up to you. Overall this is a great feature and all tested as expected!
Small screen size
Which browser do you see this in, and are you able to horizontally scroll the table without a scrollbar? Ideally you should be able to see a scrollbar:
(cc @emma-sg )
Which browser do you see this in, and are you able to horizontally scroll the table without a scrollbar? Ideally you should be able to see a scrollbar:
This is in Brave, and there is a horizontal scrollbar to scroll the table, so maybe it's okay after all. I think I was just expecting the row to collapse like the workflows, but now I see many other elements in Browsertrix handle smaller screens like this table.
This is in Brave, and there is a horizontal scrollbar to scroll the table, so maybe it's okay after all. I think I was just expecting the row to collapse like the workflows, but now I see many other elements in Browsertrix handle smaller screens like this table.
It's a good call out, and I'll do a quick pass to address the inconsistent text wrapping at different screen sizes. Will link your comments to the general responsiveness improvements issue: https://github.com/webrecorder/browsertrix/issues/1348
The tag filter feels like it's missing from the crawl runs list controls — I'm not sure how useful it really is, but I think if it's not hard to add it'd be a nice addition
Agree, we could add after https://github.com/webrecorder/browsertrix/pull/2923 and before release.
I do still think we should convert the tabs on the archived items page into a filter now that we're doing this, but that could always come later
Created issue here: https://github.com/webrecorder/browsertrix/issues/2956
The archived item list still needs an overhaul so it can work at smaller viewport sizes — I know Tessa also brought up scroll overflow vs wrapping as a solution as well, probably worth more discussion (but not super high priority either)
Tracking here: https://github.com/webrecorder/browsertrix/issues/1348