(Apologies for the kinda-redundant comment; I wanted to test something that required a new one.) So if I post a comment and then immediately—while it’s showing as an empty comment—close the window, then the thing-showing-as-an-empty-comment still shows up empty in other windows but can be edited and has all its actual content. So I’m guessing there’s some nontrivial rendering process that happens in the background on the server, and until that’s done the “rendered” version of the comment is whatever it used to be, which for a new comment is empty?
If so, then (what I assume to be) the fact that this “rendering” process is slow enough to be worth trying to do in the background seems pretty scary. How can that not be really quick?
The problem is actually not that the rendering itself is not quick. The rendering itself actually takes practically no time. I just looked into it, and the reason this is taking so long is that while the client renders the comment, it actually waits until the next server polling interval (every 20 seconds on production) to display it, which is actually a quite easy-to-fix bug.
(Apologies for the kinda-redundant comment; I wanted to test something that required a new one.) So if I post a comment and then immediately—while it’s showing as an empty comment—close the window, then the thing-showing-as-an-empty-comment still shows up empty in other windows but can be edited and has all its actual content. So I’m guessing there’s some nontrivial rendering process that happens in the background on the server, and until that’s done the “rendered” version of the comment is whatever it used to be, which for a new comment is empty?
If so, then (what I assume to be) the fact that this “rendering” process is slow enough to be worth trying to do in the background seems pretty scary. How can that not be really quick?
The problem is actually not that the rendering itself is not quick. The rendering itself actually takes practically no time. I just looked into it, and the reason this is taking so long is that while the client renders the comment, it actually waits until the next server polling interval (every 20 seconds on production) to display it, which is actually a quite easy-to-fix bug.