I've already brought it up before as a bug report (ummm, I don't recall exactly when, in February or March or something?) and was told it's something they're aware of as a bug and are working on. Apparently the issue is that many of the coders here used to code for LJ and have seen the LJ code that solves this issue, and that code is proprietary, so anyone who's seen that code isn't allowed to code the solution here b/c it would be too similar and they'd be accused of stealing code or something. So they told me they needed to wait until someone who hadn't seen the LJ code came along and coded it.
Due to this response and their treatment of it as a bug, I assumed it wasn't the type of thing I'd have to submit as a suggestion. I have just been waiting and hoping someone will fix that bug soon.
no subject
Due to this response and their treatment of it as a bug, I assumed it wasn't the type of thing I'd have to submit as a suggestion. I have just been waiting and hoping someone will fix that bug soon.