- **status**: review --> in-progress
- **Comment**:
Good progress. Hope you don't mind getting into the details now, but there are
a lot of details for this :)
* there's an unnecessary call to /nf/markdown_to_html is made when leaving
preview mode
* preview doesn't style preformatted text (e.g. 4-space indented block)
properly. Should be a fixed-width font
* Is it possible to make `<tab>` insert 4 spaces instead of a literal tab? to
be consistent with how we've done it previously. Might get messy if people
edit existing content and get a mix of tabs and spaces. Looks like
`indentWithTabs` and `tabSize` settings will do it.
* the initial editor height for comments seems a bit too high, compared to
before
* the styles for editing labels (e.g. on ticket edit) seem to have gotten
overridden or something. Not sure what happened, but I'm not seeing the blue
boxes with 'x' for each label.
* Last, this is an existing bug but I just found it and maybe you want to look
at it while you're working on this stuff. If not, we can do a separate ticket
for it. When editing a comment, or composing a new reply, a tiny width causing
wrapping can happen in during preview. Example text to produce this problem:
* qwert
12345678901234567890
---
** [tickets:#7897] Live syntax highlighting for markdown editing**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** 42cc sf-8 ux sf-current
**Created:** Mon Jun 15, 2015 02:30 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 16, 2015 08:08 AM UTC
**Owner:** Igor Bondarenko
An editor like https://github.com/lepture/editor which shows some Markdown
style rendering as you are editing (not full WYSIWYG though) could be very
helpful. Demo at http://lab.lepture.com/editor/
We should figure out how to change the help & preview buttons to use our help &
preview URLs. However I don't think we should try to customize the syntax
highlighting for our customizations (e.g. `~~~~`, artifact links, etc) yet.
Can be a followup ticket.
I like this because it doesn't attempt to do a full WYSIWYG exact render, so we
don't have to worry about some of our customizations. Yet it does do enough
formatting that people will notice if they unintentionally cause formatting
with a `_` or a `*`. And it even helps with the sneaky gotcha of a bullet list
without a preceding blank line (it doesn't work, it is rendered as italics)
(This idea came from discussion on [#6822])
---
Sent from forge-allura.apache.org because [email protected] is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
