The Renaissance Man (unixronin) wrote in suggestions,
The Renaissance Man

Consistent quoting

Consistent quoting

Short, concise description of the idea
The "Quote" button is useful, but would be more useful if the results of using it were consistent. At present, it generates different HTML tags depending on the contents.

Full description of the idea
While the Quote button is a useful feature, its behavior is annoyingly inconsistent. If the selection quoted is entirely contained within a single line, i.e. contains no line breaks, then the Quote button generates a <q> tag, and the quoted text (absent any additional CSS customization by the journal owner) renders as plain text enclosed in doublequotes, with no indent. If, on the other hand, the quoted selection contains a line break, it is enclosed instead in a <blockquote> tag, and (again, in the absence of any additional CSS customization) renders as block indented, without quotation marks.

This inconsistency means that there is no way to have quoted text in comments look the same regardless of what was quoted. This, in turn, means it's not always possible to see at a glance what text in a comment is autoquoted from the previous post, and what is the commenter quoting from somewhere else entirely. If the Quote button ALWAYS consistently generated a known tag -- preferably the <q> tag, so avoid conflicting with user blockquotes -- comment quotes could be unambiguous, and consistently formattable by the journal owner.

Quite honestly, the current Quote button is too "smart" for its own good. The result is that many people I know -- myself included -- simply don't use it, because if we use it we'll have to fix the HTML by hand anyway unless we want it to (frankly) look like crap.

An ordered list of benefits
  • Unambiguous identification of quoted text in comments
  • More consistent appearance to comments
  • Ability to consistently format quoted comment text in your LJ style without breaking the formatting of other text elements

An ordered list of problems/issues involved
  • I don't see any downsides to this change.

An organized list, or a few short paragraphs detailing suggestions for implementation
  • Really, all this would take is to simplify the function behind the Quote button to treat all selections consistently, instead of outsmarting itself.
Tags: comments, markup, § rejected
  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded