Re: [w3c/editing] indent elements in different lines created by forced breaks <br> (#190)

Well, I feel Firefox and Edge behavior is better because it does not make sense to wrap each line with new `<div>` elements. If Chrome/Safari stops it, I guess that they can omit scanning `<br>` elements in the `indent` command target. That makes them faster.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/190#issuecomment-461251945