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.
No, seriously, this commit breaks everything if you open a reply.
It's k, though, that's why this branch exists: so I can break it
all without harming end users and stable development.
Holy carp, though, the amount of errors thrown!
Obviously to start, I want to make adding and removing callbacks
simpler, because I'm going to need to be disabling and enabling
features on the fly quite a lot, I'm guessing.
