Res facta quae tamen fingi potuit (
pauamma) wrote in
dw_dev_training2014-05-02 04:38 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Entry tags:
Question thread #19
It's time for another question thread!
The rules:
- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
The rules:
- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
Status of <lj-spoiler> integration/cut tags in comments?
I am motivated to work on this because I would like functional cuts in comments!
Re: Status of <lj-spoiler> integration/cut tags in comments?
I"ve been on the fence for it. LJ's version of the spoiler tag is inaccessible, doesn't work if you don't have JS enabled (and, worse, if you don't have JS enabled it just shows you the spoiler), and is really freakin' ugly in terms of quality-of-code. Creating a "cut tags in comments" thing that is not LJ's spoiler tag is a major UI overhaul that would be really, really easy to do poorly (as witness LJ's spoiler tag). If somebody can give me a good mockup and make it accessible, it's a definite possibility, but overall I think it's a lot harder to do well than people think at first glance.