feat(a11y-table): Define a standalone table component #1634

shadowbas · 2024-11-29T12:52:56Z

Add table to the app component.

shadowbas · 2024-12-05T15:06:51Z

src/app/app.component.scss

+canvastablecontainer {
+    opacity: 0;
+}
+


Would be better to instead get rid of anything canvas related in the code.

Remove this.canv and the canvas element from canvastable

shadowbas · 2024-12-05T15:07:50Z

src/app/app.component.scss

@@ -68,3 +72,10 @@
    width: 150px;
 }

+.text-primary {
+    color: #01579b;


Move to a css property

castaway · 2024-12-09T11:45:09Z

Initial thoughts

I'd like to keep the abstraction for the messagedisplay and column lists - for column lists especially we have a plan to allow users to rearrange them, so they should ideally not be defined in the template - canvastable is the only place messagedisplay is used, so it can be improved if needed for this feature
messagedisplay for example already has the ability to return selectedMessageIds for each possible type of display, so I don't think it makes sense to redo that (confusingly ;)
there's still a fair amount of this.canvastable.rows references in app.component.ts that presumably still need changing

shadowbas · 2025-01-06T15:16:35Z

src/app/app.component.ts

+  async enrichRows() {
+    const { start, end } = this.renderedRange
+
+    this.rows = await Promise.all(mapOverIndexes(async (value) => {


This might cause a race condition. When renderedRange changes twice; it might happen that the first range change resolves later than the second range change.

Find a way to merge resolved arrays in a way that will keep the latest and not overwrite fetched rows

shadowbas · 2025-01-29T11:24:29Z

src/app/accessible-table/accessible-table.component.html

@@ -0,0 +1,13 @@
+<cdk-virtual-scroll-viewport [itemSize]="firstRowHeight" class="email-viewport">


Rename to virtual-scroll-table.component

shadowbas · 2025-01-29T11:26:11Z

src/app/accessible-table/accessible-table.component.ts

+import { debounceTime } from 'rxjs/operators';
+
+@Component({
+  selector: 'app-accessible-table',


Rename to app-virtual-scroll-table

shadowbas · 2025-01-29T11:28:07Z

src/app/app.component.html

+                      <td class="checkbox-cell">
+                        <mat-checkbox
+                          (click)="onCheckboxClick($event, item, index)"
+                          [checked]="rowsSelectionModel.isSelected(item)"


Remove event listener from the skeleton version of a row.

shadowbas · 2025-01-29T11:34:09Z

src/app/app.component.html

+              (sortToggled)="updateSearch(true)">
+            </canvastablecontainer>
+
+            <app-accessible-table


@castaway , at some point I think it makes sense to move this table definition into its own component.

I believe that time to be when we want to re-use this table in other places either because we want to have better routing for folders or for some other reason that requires re-use.

Its that sizable that I'd suggest earlier rather than later (since app.component.html is chunky already)

shadowbas · 2025-01-29T11:34:50Z

src/app/app.component.scss

+
+}
+
+.skeleton-bone {


Move skeleton styles to global styles.

shadowbas · 2025-01-29T11:40:39Z

src/app/human-bytes.pipe.ts

+
+    const result = (value / Math.pow(base, exponent)).toFixed(decimalPlaces);
+    return `${parseFloat(result)} ${suffixes[exponent]}`;
+  }


It appears we have a function in src/app/messagetable/messagetablerow.ts. The converting of a number that represents the amount of bytes to a human readable format is not specific to messagetable.

Make a human-readable utility module and use that here and in the messagetablerow.ts.

shadowbas · 2025-01-29T11:43:58Z

src/app/models/bindable-selection-model.ts

+    const selection = (this.selectionModel.isMultipleSelection() ? items : [items]) as T[];
+    this.selectionModel.setSelection(...selection)
+  }
+}


Angular allows for two way binding in the template. Here we wrap the angular Selection model and add the selected property to be used for binding.

shadowbas · 2025-01-29T11:55:54Z

src/app/models/filter-selection-model.ts

+      }
+    });
+  }
+}


A SelectionModel that takes a predicate which is used to filter items selected using the .select(...items) method. This is handy to prevent selecting items that have not been loaded yet. This is relevant when doing a range select which contains items that have not been loaded into array yet.

shadowbas · 2025-01-29T11:57:55Z

src/app/resizable-button/resizable-button.component.ts

+  @HostListener('window:resize')
+  onWindowResize() {
+    this.resetWidth();
+  }


Should this be here? When do we want to reset the widths?

shadowbas · 2025-01-29T12:00:40Z

src/app/websocketsearch/websocketsearchmaillist.ts

+        size: this.getRow(rowIndex).size,
+      };
+    }
+


@castaway , could you please help with how to test the websocketsearchmaillist?

websocketsearch is used when:

The index sync is turned off

A search is made (this hits an API which returns search results from the index on the server)

shadowbas · 2025-01-29T15:57:32Z

src/app/xapian/searchmessagedisplay.ts

    } catch (e) {
      // This shouldnt happen, it means something changed the stored
      // data without updating the messagedisplay rows.
-      console.log('Tried to lookup ' + index + ' in searchIndex, isnt there! ' + e);
+      console.error('Tried to lookup ' + index + ' in searchIndex, isnt there! ' + e);


Change + e to , e for more useful log in console

shadowbas · 2025-01-29T15:58:50Z

src/app/xapian/searchmessagedisplay.ts

+      seen: this.searchService.getDocData(this.getRowId(index)).seen,
+    };
+
+    if (app.viewmode === 'conversations') {


Add the conversation count also to the accessible table as it was in canvastable.

shadowbas · 2025-01-29T15:59:38Z

src/app/xapian/searchservice.ts

            // console.log(`${f}`);
            // console.log(FS.stat(`${this.partitionsdir}/${f}`));
-          });
+          // });


Removed the look as it does nothing but block the thread. Easy performance win

castaway · 2025-02-04T11:52:50Z

Notes while testing/poking around - mostly comparing to existing prod (since we didnt write a spec..)
1.

Clicking on the Arrow seems to do nothing other than make the arrow disappear (does not redisplay sorted date in reverse) - ah! the arrow is just a display of the current direction? It looks like its actionable.. clicking on the arrow is how the current one sorts.

(new change on prod) - the icons for move/trash etc for selected messages - need to disappear or better grey-out when no messages are selected
Is there no "show message list and mailviewer at the same time in horizontal mode"? it seems to go full screen only and not allow me to drag it smaller - I was wrong, there is, it just somehow defaulted to full height (ignored my prefs?)
open message, full height/display mailviewer - refresh page - it looks like the "sync index" prompt appears and then is covered up by the opened message - not sure if this is an issue in prod already, dont usually view it full height
Drag messages to folder - missing the drag-image showing the messages being dragged
This one is a bit weird - I keep having to do things twice - for example I visited the Overview, viewed a list of emails, which link to the mail view (for example https://rmmstage02.runbox.com/app/#Inbox:12813748 (user [email protected]) - clicking on this link took me to the #Inbox page, not opening the specific message. I went back to the Overview (forward, I clicked on Overview again), re-clicked on the message link, and the 2nd time it did open the individual message in the mailview
Opened a message / mailview (from the Overview), the list jumps/scrolls to show that row (good!) , I closed the message (horizontal view), more of the message list was displayed - but it didnt fill the available space / load more messages:

.. If I scroll down from that I lose even more messagelist height:
Threaded view doesnt seem to work for me, after I chose it I got this (ongoing):

.. and this in the devtools:

TypeError: Cannot read properties of undefined (reading '1')
    at lp.getRowData (searchmessagedisplay.ts:244:29)
    at app.component.ts:1500:48
    at Generator.next (<anonymous>)```

10. After testing threading I switched it off and tried unread only, which worked.. then I turned off the index, scrolled, turned unread only off/on, and its not filtering:

![2025-02-04 13 49 33 rmmstage02 runbox com 7bc055abc18b](https://github.com/user-attachments/assets/101e1789-63f0-4e7a-aeaf-7a04eff43940)

castaway · 2025-02-04T16:09:52Z

Starting new comment since that one seems full:
11. Select-drag over checkboxes with mouse (works on prod) - doesnt here
12. No way of "select all on page" / "select all in folder" that I can see?

castaway · 2025-02-05T16:06:17Z

Another odd issue: If I navigate away from the Inbox/message list (eg to Settings), then back via clicking on the menus at the top of the app - the message list shows up empty apart from the checkboxes.. If I swap browser tabs (eg to mattermost and back) then the list reappears ...

castaway · 2025-03-19T16:25:40Z

Some testing this afternoon:

The fetch of message contents according to the current message list - this should happen in both the index-sync and index-off modes
If I click "Stop Index Synchronisation" things go a bit screwy! (hmm not always tho.. yay)

shadowbas · 2025-03-31T12:47:11Z

Some testing this afternoon:

The fetch of message contents according to the current message list - this should happen in both the index-sync and index-off modes

If I click "Stop Index Synchronisation" things go a bit screwy! (hmm not always tho.. yay)

@castaway , I am unable to reproduce this on my account. I could do a null check and drop the message when it is null.

gtandersen · 2025-05-12T08:30:47Z

Improved default column widths:

- Improves on the less accessible canvastable. - Introduces multi select using ctrl and shift. - Reduces memory footprint by a good margin.

castaway

Some queries/changes

castaway · 2025-02-04T15:55:58Z

src/app/app.component.html

+              (sortToggled)="updateSearch(true)">
+            </canvastablecontainer>
+
+            <app-accessible-table


Its that sizable that I'd suggest earlier rather than later (since app.component.html is chunky already)

castaway · 2025-06-18T11:00:37Z

src/app/xapian/searchmessagedisplay.ts

@@ -32,7 +32,7 @@ export class SearchMessageDisplay extends MessageDisplay {
  }

  getRowSeen(index: number): boolean {
-    return this.searchService.getDocData(this.rows[index][0]).seen ? false : true;
+    return this.searchService.getDocData(this.getRowId(index)).seen;


I am a bit confused how / why, this state of this boolean (it was "if seen then return false" .. yes I know its weird), has changed, but the same method in messagelist.ts didnt.. so now the two are returning different states for seen yes/no ?

I'll just revert it to what it was

castaway · 2025-06-18T11:02:45Z

src/app/resizable-button/resizable-button.component.html

General comment for all the new components: The existing code tends to have as a major structure, top level directories are areas of the application, canvastable, mailviewer etc (more or less), and the components for an area go inside that directory - or in common/ if they are used by multiple areas .. so could we move the new components into sub-directories appropriately please

app.component is indeed very big. We should have more routes defined which would result in a smaller app.component. I suggest that instead of wrapping it in a component which requires passing loads of @Inputs or imports.

src/app/canvastable/canvastable.ts

castaway · 2025-06-18T11:04:28Z

src/app/websocketsearch/websocketsearchmaillist.ts

+        size: this.getRow(rowIndex).size,
+      };
+    }
+


websocketsearch is used when:

The index sync is turned off

A search is made (this hits an API which returns search results from the index on the server)

…oll table

…ual scroll table

…nt virtual scroll table

…Implement virtual scroll table

…list): Implement virtual scroll table

castaway · 2025-06-18T11:39:00Z

src/app/app.component.ts

+  }
+
+  updateRows() {
+    this.rows = this.canvastable?.rows?.rows ? [...this.canvastable.rows.rows] : []


If this is "fetch rows we just stored in canvastable, back out again", then it would be less complex to change setMessageDisplay to write to this.rows directly

…essage-list): Implement virtual scroll table

… feat(message-list): Implement virtual scroll table

… fixup! feat(message-list): Implement virtual scroll table

castaway · 2025-06-24T10:24:07Z

src/app/app.component.ts

-          };
-          // Send to the messageCache in the worker, so we can add the text to the index:
-          if(updateWorker.size > 0) {
-            this.searchService.indexWorker.postMessage({'action': PostMessageAction.messageCache, 'updates': updateWorker });


Where does this happen now? (I can't find a replacement for this code)

Not sure what I broke by removing this. I'll add it to the todo of this PR.

castaway · 2025-07-16T12:11:53Z

Canvastable use review:

Summary:

MessageDisplay object (the one setMessageDisplay sets/updates) - needs to move somewhere else (into app.component.ts?), and all calls to it changed to use the new one
- Most of its purpose is to track which rows are available, which are selected, which are checked and so on, while being able to cope with the 3 different variants of row storage. It looks like the checked/selected etc logic has been moved into new classes for the virtual table, so any code that expects to be able to change/select/clear the selected/checked rows etc needs to be changed to use the new models? (or the models need to use the MessageDisplay)
- In particular, the logic is supposed to be such that when the user does an action, eg deletes a message, the existing MessageDisplay rows are updated (see eg canvastable.removeMessages), then we set hasChanges, and the message list display instantly changes. Now that the rows are extracted from the MessageDisplay, and stored as a copy in this.rows, this "instant update" cannot happen - how we do we fix this ?
Preferences - the existing code stores the "showContextPreview" and "columnWidths" preferences after users change them
- this needs to happen for the new system (we are not storing column widths prefs in virtual table yet)
- the showContextPreview value that is stored in canvastable can just move to app.component.ts
- columnwidths should also be resized/stretched accordingly (not reset to default), if the browser window size changes
Keyboard events - the app.component.ts has keyboard events for scroll up/down, we need to port these to the virtual table, or decide to lose them
Loading new message service (non-index) data - I cant see/understand where the virtual table loads more rows, for the REST API data - it used to use the scrollLimitHit event to call messagelistservice.requestMoreData .. there are no new calls to this, how does it work now?
jumpToOpenMessage - this was called from outside the canvastable, so that if the message that the user selected to open, did NOT open (this is possible if there are errors loading the message), the scroll/jump to top did not happen. Does the virtual table cope with this? (not jumping if the pane does not open)
canvastable.topindex - replace with whatever makes the virtualtable jump to the top from outside (used after switching from Index to API based data)
More, see NOTES below:

Raw NOTES:

canvastable.showContentTextPreview, pulled out of preferences in app.component.ts:336 / 406 , stored in canvastable, displayed if there is a canvastable object, in app.component.html:336/559/656/677
- Suggestion: store in an app.component.ts variable instead?
- adjust all uses of it to use app. instead of canvastable
canvastable.rows.openedRowIndex / canvastable.scrollUp / canvastable.scrollDown - in keyboardevent listener
- app.component.ts:272
- I assume this has been replaced in new virtual table and can be removed?
canvastable.columnWidths / canvasNamedColumnWidthsBySet the saved columnwidth preferences
- Does the new table save the column widths after the columns are re-sized? if not this should be saved using the preferences system - after a test it seems like it does not
- fix saving code, save widths, remove canvastable columnWidths code
canvastable.jumpToOpenMessage - selecting fragment message and scrolling to it in the message list are separate actions in the canvastable class. JumpToMessage is also used by updateMessageListHeight (which is called by afterLoadMessage when we open one) to scroll the list to that message
- it seems the virtual table does the "scroll to and open to fragment" and "scroll to opened message" in some other fashion, so updateMessageListHeight, afterLoadMessage and jumpToOpenMessage appear to be redundant now. As is the afterLoadMessage usage in mailviewer/singlemailviewer.component
- does the new version cope if the message its asked to open doesnt open ? (aka the message loader cant find it) does it scroll anyway? (that would be an odd visual I think)
- See logic in singlemailviewer - if the requested message id has some kind of issue, the mailviewer self-closes
canvastable.scrollLimitHit
- app.component.ts:447 this is how the existing code decides to load another page of messages, when viewing the list in non-index mode
- the new virtual table seems to do this, though I can't see where/how !? Very confused by this one, where does it prompt the messagelist service for more data?
canvastable.canvasResizedSubject
- app.component.ts:451
- I suspect this can go away entirely, its just stretching the columns to fit a new / resized window width - I assume the virtual table can do this?
- tested - it does not seem to, so we should implement that.
canvastable.rows.removeMessages
- app.component.ts:720,843,1147,1184,
- this reaches into the MessageDisplay rows and removes some messages
- it is meant to cause an instant update of the listed messages being displayed, as the virtual table code is only operating on list changes after setMessageDisplay changes them (which is after the backend update), presumably thats slower..? (especially on slow network connections)
- we should store the MessageDisplay rows somewhere not the canvastable, I suspect only app.component needs to talk to it, so probably in there.
- OR if the virtual table has its own storage for "which rows are displayed and their states (selected checked etc), change to use that
canvastable.topindex
- app.component.ts:862
- this should jump the message list to the first item, after deleting the index, looks like the virtual table does not do this yet.
- it also emptys the messagedisplay (canvastable.rows) - not clear if this is necessary to keep
setMessageDisplay - setting canvastable.rows etc
- app.component.ts:886 et al
- manages which rows should be displayed (the messagedisplay) - we should store the current messagedisplay .. somewhere, and it should be used to display the list (not the extracted sublist of rows)
canvastable.columns
- app.component.ts:924
- this sets the visual look of the columns for the currently chosen messagedisplay, unused if that logic is now elsewhere? (where is it?) (Sent vs From etc)
canvastable.rows.filterBy
- app.component.ts:934
- filters visible messages by the unread/search options - change to point to whereever the MessageDisplay object ends up
canvastable.hasChanges
- tons of places - I assume no longer needed, as it was picked up by the repaint loop on the canvas
- how does external code tell the virtual table to update because its content has changed now? just by setting rows ?
canvastable.rows.getRowMessageId, .rows.rowSelected, etc
- app.component.ts:964, 971-975
- sets the urlFragment to the opened message id - change this to fetch from whereever the MessageDisplay object ends up..
- note it checks hasChanges, so that we dont update it constantly, we need some equivalent
- this also tells the singlemailviewer which message it is opening (line 975)
rowSelected
- app.component.ts:951
- this is the whole "which rows are selected and how" (checked, highlighted etcetc) management code for the canvastable view - it looks like the virtual table sidesteps all that and has its own row view management. This is most of the point of the existance of MessageDisplay.. so anything using that either needs to be changed to use the new models, or the new models need to be replaced with MessageDisplay
canvastable.rows.getCurrentRow()[2] !== '1')
- app.component.ts:983
- when viewing threads/conversations this only shows the "single conversation" view, when the conversation has more than one item in it (if there's only one item, it opens the email instead)
- NB: testing on allytable - the Count should show "1" for threads with one item in, and when clicking on a thread with 1 item, it should just open the email
canvastable.rows.getCurrentRow()[0], 1)
- app.component.ts:990
- updates the search/list of displayed messages using just the conversation, from the index
- update to use whereever we move MessageDisplay object to (or whatever the virtualtable is using for current messagelist status)
canvastable.rows.clearOpenedRow
- app.component.ts:1092
- de-highlights the greyed row in the message list, showing which email is currently open (after mailviewer close)
- replace with however the virtualtable knows which row is "open"
canvastable.scrollTop
- app.component.ts:1272
- Another "scroll to top of list" after switching folders - I think the virtual table does this already in some other way, so move ?
resetColumns
- app.component.ts:1276
- sets the correct set of columns visible, for the current MessageDisplay style, called various places
- adjust to set virtualtable column sets ?
canvastable.scrollTop
- app.component.ts:1412
- scrolls to top of list, after new search (NB search includes just listing all the messages)
- I cant find anywhere that actually passes "noscroll=true" so its possible this logic is redundant
canvastable.horizScroll
- app.component.ts:1442
- Looks like is entirely redundant now
canvastable.autoAdjustColumnWidths
- app.component.ts:1448
- set column widths, mostly called after changing which columns are displayed, probably redundant now?
this.canvastable.rows.rows
- app.component.ts:1493
- use the MessageDisplay object, whereever we end up storing it? Ditto in enrichRows
- Why do we set this.rows to the above, and then have enrichRows work on canvastable.rows ? seems a bit redundent to do both

castaway · 2025-07-17T11:47:57Z

Ah just noticed this part too:

      const {data: column, direction} = this.orderSelectionModel.selected

      if (direction === Direction.None) {
         this.canvastablecontainer.sortColumn = 2;
         this.canvastablecontainer.sortDescending = true;
       } else {
         this.canvastablecontainer.sortColumn = column;
         this.canvastablecontainer.sortDescending = Direction.Descending === direction;
       }

shadowbas requested review from castaway and gtandersen November 29, 2024 12:52

shadowbas force-pushed the shadowbas/feat-accessible-table branch from 596aec9 to 972eb6a Compare December 5, 2024 14:08

shadowbas commented Dec 5, 2024

View reviewed changes

gtandersen approved these changes Dec 5, 2024

View reviewed changes

shadowbas requested a review from gtandersen December 12, 2024 12:10

shadowbas commented Jan 6, 2025

View reviewed changes

shadowbas force-pushed the shadowbas/feat-accessible-table branch from 7c02014 to 62b6d40 Compare January 14, 2025 17:42

shadowbas commented Jan 29, 2025

View reviewed changes

src/app/app.component.scss Outdated

}

.skeleton-bone {

Copy link

Contributor Author

shadowbas Jan 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move skeleton styles to global styles.

shadowbas commented Jan 29, 2025

View reviewed changes

shadowbas force-pushed the shadowbas/feat-accessible-table branch from fef59c7 to 67fd747 Compare February 4, 2025 16:34

shadowbas force-pushed the shadowbas/feat-accessible-table branch from 44e5ea1 to 92576fa Compare March 10, 2025 16:10

shadowbas force-pushed the shadowbas/feat-accessible-table branch from 36c5e72 to c38c2fe Compare April 4, 2025 12:28

shadowbas force-pushed the shadowbas/feat-accessible-table branch 2 times, most recently from 871291d to ef1226e Compare April 18, 2025 13:34

shadowbas force-pushed the shadowbas/feat-accessible-table branch from 27a5552 to 108bd66 Compare May 5, 2025 12:46

shadowbas force-pushed the shadowbas/feat-accessible-table branch 4 times, most recently from 6c96136 to f57a331 Compare May 20, 2025 16:28

shadowbas force-pushed the shadowbas/feat-accessible-table branch from 99a1649 to aff3997 Compare June 4, 2025 10:13

shadowbas force-pushed the shadowbas/feat-accessible-table branch from aff3997 to c45faa0 Compare June 17, 2025 12:20

shadowbas and others added 2 commits June 17, 2025 15:23

fix(commit-lint): allow hyphen in commit subject

1e8c345

feat(message-list): Implement virtual scroll table

3fb375b

- Improves on the less accessible canvastable. - Introduces multi select using ctrl and shift. - Reduces memory footprint by a good margin.

shadowbas force-pushed the shadowbas/feat-accessible-table branch from c45faa0 to 3fb375b Compare June 17, 2025 12:23

castaway requested changes Jun 18, 2025

View reviewed changes

shadowbas added 8 commits June 18, 2025 14:57

fixup! feat(message-list): Implement virtual scroll table

6984050

fixup! fixup! feat(message-list): Implement virtual scroll table

f5306f1

fixup! fixup! fixup! feat(message-list): Implement virtual scroll table

452d214

fixup! fixup! fixup! fixup! feat(message-list): Implement virtual scr…

6cea823

…oll table

fixup! fixup! fixup! fixup! fixup! feat(message-list): Implement virt…

40fccf9

…ual scroll table

fixup! fixup! fixup! fixup! fixup! fixup! feat(message-list): Impleme…

a639ed2

…nt virtual scroll table

fixup! fixup! fixup! fixup! fixup! fixup! fixup! feat(message-list): …

e98ca9a

…Implement virtual scroll table

fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! feat(message-…

f4b8f66

…list): Implement virtual scroll table

castaway requested changes Jun 18, 2025

View reviewed changes

shadowbas added 3 commits June 18, 2025 17:28

fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! feat(m…

f319700

…essage-list): Implement virtual scroll table

fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup!…

df251b7

… feat(message-list): Implement virtual scroll table

fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup!…

bf4ca21

… fixup! feat(message-list): Implement virtual scroll table

castaway reviewed Jun 24, 2025

View reviewed changes

		@@ -0,0 +1,13 @@
		<cdk-virtual-scroll-viewport [itemSize]="firstRowHeight" class="email-viewport">

feat(a11y-table): Define a standalone table component #1634

Are you sure you want to change the base?

feat(a11y-table): Define a standalone table component #1634

Uh oh!

Conversation

shadowbas commented Nov 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

castaway commented Dec 9, 2024

Uh oh!

shadowbas Jan 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shadowbas Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shadowbas Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shadowbas Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shadowbas Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shadowbas Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

castaway commented Feb 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

castaway commented Feb 4, 2025

Uh oh!

castaway commented Feb 5, 2025

Uh oh!

castaway commented Mar 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shadowbas commented Mar 31, 2025

Uh oh!

gtandersen commented May 12, 2025

Uh oh!

castaway left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

shadowbas commented Nov 29, 2024 •

edited

Loading

shadowbas Jan 6, 2025 •

edited

Loading

shadowbas Jan 29, 2025 •

edited

Loading

shadowbas Jan 29, 2025 •

edited

Loading

shadowbas Jan 29, 2025 •

edited

Loading

shadowbas Jan 29, 2025 •

edited

Loading

shadowbas Jan 29, 2025 •

edited

Loading

castaway commented Feb 4, 2025 •

edited

Loading

castaway commented Mar 19, 2025 •

edited

Loading

shadowbas Jun 18, 2025 •

edited

Loading