I verified an issue with the previous benchmark and even wrote a
more efficient method based off el.cloneNode(false);, which I would
use if cloneNode could inherit eventListeners
Speaking of events. there is still no interface for gather all
eventListeners on a given element (or its children). Apparently the
issue is that the w3c doesn't think there is a legitimate use case
for it. Heh.
Currently breaks posting.
TODO:
* Fix style switching from NSFW to SFW (SFW to NSFW works)
- It is worth noting this used to work.
* Fix post form not updating its currently selected thread.
* Fix navigation between threads in different boards (same boards
works? Maybe?)
* Handle race conditions due to pop states.
- I'm having a lot of trouble wrapping my mind around this one.
Mostly due to the fact that I have no idea where to begin with
it. But this isn't a big issue unless you pop state multiple
times within seconds.
I just need some exceptions when we try to disconnect features
that haven't even finished connecting due to threads not being
available yet.
Most of the early issues, like double-backlinks, incorrect
thumbnails, etc, have been fixed, I think. Or at least I'm no
longer running into them all the time.
It checks unread count already anyways, and the previous behavior
was causing QuoteThreading.force() to run twice, and may have
caused an issue where backlinks were doubling-up? I don't know, I'm
still looking into that issue because it's happening on the Index
as well.
I profiled this and on a 700 post thread, 30% time was spent trying
to figure out if we needed to scroll to the top of the thread or
not. I don't feel that's acceptable.
because @MayhemYDG had already done it and done it better. So I
thought mine was working when it was just his... and then
realized when I didn't disconnect it and the index was getting a
title from a thread that it wasn't working and his was.
So let's just use his code.