Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Marks always "bleeding" into new line by default

See original GitHub issue

Do you want to request a feature or report a bug?

Bug

What’s the current behavior?

Tested with v0.32.1 on Chrome/Firefox/Safari locally as well as in the examples page (below gif recorded as of today 1/24/2018): It appears that, with given two paragraphs, if there are marks on the ending text of the previous paragraph, they always carry over to the following paragraph by default.

Below are a couple issues reproduced from this bug, using the examples page. (http://recordit.co/zvPYlyFYlr)

Styling the end of the text with bold, then hitting enter to hard break leads the following paragraph to be bolded by default as well. I did search through the previous issues and from #1269 I see there was some discussion around this behavior; but I think the decision was ultimately not to support the auto carry over and let users to decide for themselves (#1273). Given this, it leads me to believe this is a bug.
Another unintuitive behavior is when you manipulate the previous paragraph (by deleting ! character), it automatically affects the following paragraph even though the edit operation was not related and done only to the first paragraph. I imagine this is rather unexpected for most use cases. (I’m not certain, but back in the days Slate used to use zero-width space to deal with empty text and such, but I don’t think the latest version does that anymore- maybe related?)

Omitting JSFiddle, because reproducible with the example page.

What’s the expected behavior?

Hard breaking on text with marks does not automatically carry over the style to the following split paragraph
Editing marks/style of a paragraph in isolation should not affect the following paragraph.

I took a quick look at splitBlock and other associated internals but I must admit, I was pretty lost in it 😅… Really appreciate Slate and the work everyone has put in - let me know in any ways I can help.