
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Is there an existing issue for this?
Describe the bug
I have a Blazor WASM page that renders a table with 16 columns of data over 4 types of objects. Each of these 4 objects only renders some of the columns and the rest are
colspan
together. I have between 400 to over 100K records. I implementedVirtualize
and it works perfectly even with the 100K rows.Now, I have a single button, outside of the
Virtualize
area but still within the containing scroller div that displays a modal. The modal code is outside of even the containing scroller. If the modal container is set todisplay: none
the checkboxes I have within theVirtualize
are quite slow (1 second for only about 400 rows) and up to 30 seconds when I have the 100K rows.Another implementation I tried where there was a razor
if
statement surrounding the modal code, when the modal was not showing, the checkboxes worked great. Once the modal is displayed, the checkbox list I have in the modal (where there are 126 choices) is very laggy, for some reason relative to how many rows are in theVirtualize
data (which has nothing to do with the modal.)I have more detail in my stack overflow post.
In the most recent update, I added it seems to have nothing to do with the modal (I thought it may have some sort of interaction issue with the virtualize and the modal on top) but that is not the problem because I put the select list below the virtualize grid.
Expected Behavior
I would like the modals to work, no matter how many components exist in it or anywhere on the page.
Steps To Reproduce
I created this from scratch (14 of the columns just really had text or expand collapse capabilities) and these all worked. Once I added the two columns that had a single checkbox in each, the Virtualize still worked. Then I moved on to the modal and that is where the lagging came in. Turns out, it does not even need to be a modal.
Exceptions (if any)
No response
.NET Version
6.0.101
Anything else?
.NET SDK (reflecting any global.json):
Version: 6.0.101
Commit: ef49f6213a
Runtime Environment:
OS Name: Windows
OS Version: 10.0.19043
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.101\
Host (useful for support):
Version: 6.0.1
Commit: 3a25a7f1cc
.NET SDKs installed:
5.0.401 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
The text was updated successfully, but these errors were encountered: