Override DOM.DEFAULT_BLOCK_TAG?

[whather]

We're using Quill to produce email HTML and seems like a lot of email clients (at least Gmail) have excessive padding on paragraph tags. Wrapping lines in a

instead of a

seems to be the fix.

Would be great to have the ability to override DOM.DEFAULT_BLOCK_TAG

[jhchen]

I think Github comments might be hiding some of your input but are you trying to say using <div> instead of <p>?

[whather]

Oh whoops, yeah they stripped them out.

Yeah wrapping in div's instead of p's

[tdharris]

We're also using Quill to produce email HTML and getting paragraph spacing where we don't want any. Something to consider, in Microsoft Word - when you hit [Enter] it does presume a new paragraph is wanted (paragraph spacing is applied). When you hit [Shift] + [Enter] - it does not create a new paragraph and simply creates a line-break. This keeps the text all contained within a single paragraph.

In Quill, there is no way to visually see a representation of the spacing that is generated from the "p" tag. For example, the editor may show:
Here is text on one line
and text on a newline

But, in reality getHTML translates this into:

Here is text on one line

and text on a new line

Essentially, the problem I see is that there is paragraph spacing when just a "br" is wanted. So same thing in regards to the first comment. Just thought I'd explain how I see it.

[jhchen]

Quill originally used a <div> but switched to <p> for semantic correctness but since it's causing issues we'll switch back in the next release.

[EmilStenstrom]

I fully agree with @tdharris here, supporting shift + enter should be a a priority. If you want to use div, that's fine, but <div>text</div><div>text</div> should be output with an enter, and <div>text<br>text</div> with shift + enter.

Should I start a new issue with this or is this one a good place to track this feature suggestion?

[jhchen]

Should be a separate issue I think.

[EmilStenstrom]

@tdharris I've made a separate issue to track the shift + enter requirement: #252

[pmarreck]

Quill is still using p tags when you hit Return in an editor, and it's (still) messing up my attempts to have people edit an html email signature (due to the aforementioned issues)... what's the deal?