News for hackers. Stuff that matters.
Re:Quill – A cross browser rich text editor with an API by oneeyedpigeon on Sunday October 25, 2015 @11:38AM (#10447150)
What kind of markup will this produce? Currently, I'm left guessing as to whether or not it will be the same as I see when I inspect the editor itself. It claims "semantic markup", yet it offers styling tools alongside semantic ones.
Re:Quill – A cross browser rich text editor with an API by dgreensp on Sunday October 25, 2015 @12:39PM (#10447348)
It produces "rich text" in a clean JSON format, which is one of Quill's strengths IMO. It's also what enables it to be used for real-time collaborative editing across browsers without any weirdness about HTML normalization.
Re:Quill – A cross browser rich text editor with an API by chrisutz on Sunday October 25, 2015 @12:33PM (#10447322)
I use Quill on my site to allow trusted but non-technical users to write rich text. It was easy to configure so it only allows a strict subset of tags. My users have been using it for a few months and haven't managed to slip in any disallowed tags, attributes, or styles.
Re:Quill – A cross browser rich text editor with an API by nlte on Sunday October 25, 2015 @01:07PM (#10447456)
I did the same. But those non-technical users still ask why they can't paint their text red, right-align paragraphs and insert as many line breaks as their good taste suggests. So it can't really work unless they agree to get a bit technical and understand what semantic markup and CSS are. And then, I'd really prefer to teach them some basic markdown and have them use a markdown editor, only so they can stop believing that "what they see is they get".
Re:Quill – A cross browser rich text editor with an API by jhchen on Sunday October 25, 2015 @09:02PM (#10449122)
It produces semantic markup when it can, but in some cases such as font color, there is no semantic representation so it uses the most cross browser/application implementation, which is inline styles.
Re:Quill – A cross browser rich text editor with an API by andybak on Sunday October 25, 2015 @05:44PM (#10448566)
Explain what you mean by 'semantic markup'. I find people mean the term in two ways: so trivially it's uninteresting or so unrealistic it's implausible.
Re:Quill – A cross browser rich text editor with an API by oneeyedpigeon on Monday October 26, 2015 @04:54AM (#10450168)
In my experience, the most common meaning of 'semantic' is 'non-presentational'. For example:

  <font color="#ff0000">hello, world</font>
is non-semantic because it's referring purely to presentation, rather than meaning. I'm not just being obtuse, this is a real-world requirement since our editors need to be able to mark things up according to meaning, but not randomly screw around with our design. I admit there's a blurry line, exemplified by the W3C's redefinition of the 'b' element.
Re:Quill – A cross browser rich text editor with an API by andybak on Friday October 30, 2015 @04:31AM (#10476692)
I'd concur that is a good example of 'non-semantic' but what's trickier is to agree on what 'semantic' markup looks like. Short of well-executed microdata - I've always felt that a lot of claims about markup best-practice smacked of cargo-culting.

It's always worth asking the question: "semantic for whom"? i.e. who is the consumer. That clears away a lot of fog.