Only fixing the bug described by the summary is simple, but as the testcase, when `<br>` element follows invisible white-space only text nodes and/or empty inline elements like `<span>`, the behavior of Blink and WebKit is odd. They put text to the last visible text node, i.e., before the `<span>` in the testcase. But if I fix this with a simple patch, Gecko puts text immed before the `<br>`. Emulating the other browsers' behavior reqires complicated patch, so, I'd like to put it off later. Reporter: Will you have any problems if I don't fix the insertion position difference here?
Bug 1716863 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Only fixing the bug described by the summary is simple, but as the testcase, when `<br>` element follows invisible white-space only text nodes and/or empty inline elements like `<span>`, the behavior of Blink and WebKit is odd. They put text to the last visible text node, i.e., before the `<span>` in the testcase. But if I fix this with a simple patch, Gecko puts text immediately before the `<br>`. Emulating the other browsers' behavior reqires complicated patch, so, I'd like to put it off later. Reporter: Will you have any problems if I don't fix the insertion position difference here?