@anon
sign up
@anon
sign up
pull down to refresh
0 sats
\
0 replies
\
@WeAreAllSatoshi
OP
20 Apr
\
on: Testing https://github.com/stackernews/stacker.news/issues/728
meta
Tracing the code client side, it does seem to get to
toaster.success(message)
, but no toast appears. We are probably re-rendering the toast context too many times since new posts result in a page navigation and are therefore losing the toast entry.
write
preview
reply
100 sats
toaster.success(message), but no toast appears. We are probably re-rendering the toast context too many times since new posts result in a page navigation and are therefore losing the toast entry.