I investigated the behavior of Chrome a bit more. It seems that if the pasting data has white space at least one, they replace the line break with a white space. (I could not add a line break in the table in markdown, add `<br>` instead.) | name | input | result | | - | - | - | | keywords without white space | 123<br>45<br>6 | 123456 | | keywords with white space | 123<br>45 6 | 123 45 6 | | url without white space | http://exam<br>ple.<br>com | http://example.com | | url with white space | http://exam<br>ple.co m | http://exam ple.co m | | data url without white space | data:text/html,123<br>45<br>6 | data:text/html,123456 | | data url with white space | data:text/html,123<br>45 6 | data:text/html,123 45 6 | Chrome is consistent in the sense that its behavior changes depending on whether there is whitespace or not. However, is not consistent for the data type. I think we’d better take consistency by the data type as we are doing. For the data url, when the content expresses by base64, remove line break simply. Otherwise, replace line break with white space. | name | input | result | | - | - | - | | keywords without white space | 123<br>45<br>6 | 123 45 6 | | keywords with white space | 123<br>45 6 | 123 45 6 | | url without white space | http://exam<br>ple.<br>com | http://example.com | | url with white space | http://exam<br>ple.co m | http://example.co m | | data url without white space | data:text/html,123<br>45<br>6 | data:text/html,123 45 6 | | data url with white space | data:text/html,123<br>45 6 | data:text/html,123 45 6 | | base64 data url without white space | data:text/html;base64,123<br>45<br>6 | data:text/html;base64,123456 | | base64 data url with white space | data:text/html;base64,123<br>45 6 | data:text/html;base64,12345 6 | I will implement as above, but if you have opinions, please let me know.
Bug 1823690 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I investigated the behavior of Chrome a bit more. It seems that if the pasting data has white space at least one, they replace the line break with a white space. (I could not add a line break in the table in markdown, add `<br>` instead.) | name | input | result | | - | - | - | | keywords without white space | 123<br>45<br>6 | 123456 | | keywords with white space | 123<br>45 6 | 123 45 6 | | url without white space | http://exam<br>ple.<br>com | http://example.com | | url with white space | http://exam<br>ple.co m | http://exam ple.co m | | data url without white space | data:text/html,123<br>45<br>6 | data:text/html,123456 | | data url with white space | data:text/html,123<br>45 6 | data:text/html,123 45 6 | Chrome is consistent in the sense that its behavior changes depending on whether there is whitespace or not. However, is not consistent for the data type. For ours, I think we’d better take consistency by the data type as we are doing. For the data url, when the content expresses by base64, remove line break simply. Otherwise, replace line break with white space. | name | input | result | | - | - | - | | keywords without white space | 123<br>45<br>6 | 123 45 6 | | keywords with white space | 123<br>45 6 | 123 45 6 | | url without white space | http://exam<br>ple.<br>com | http://example.com | | url with white space | http://exam<br>ple.co m | http://example.co m | | data url without white space | data:text/html,123<br>45<br>6 | data:text/html,123 45 6 | | data url with white space | data:text/html,123<br>45 6 | data:text/html,123 45 6 | | base64 data url without white space | data:text/html;base64,123<br>45<br>6 | data:text/html;base64,123456 | | base64 data url with white space | data:text/html;base64,123<br>45 6 | data:text/html;base64,12345 6 | I will implement as above, but if you have opinions, please let me know.
I investigated the behavior of Chrome a bit more. It seems that if the pasting data has white space at least one, they replace the line break with a white space. (I could not add a line break in the table in markdown, add `<br>` instead.) | name | input | result | | - | - | - | | keywords without white space | 123<br>45<br>6 | 123456 | | keywords with white space | 123<br>45 6 | 123 45 6 | | url without white space | http://exam<br>ple.<br>com | http://example.com | | url with white space | http://exam<br>ple.co m | http://exam ple.co m | | data url without white space | data:text/html,123<br>45<br>6 | data:text/html,123456 | | data url with white space | data:text/html,123<br>45 6 | data:text/html,123 45 6 | Chrome is consistent in the sense that its behavior changes depending on whether there is whitespace or not. However, is not consistent for the data type. For ours, I think we’d better take consistency by the data type as we are doing. For the data url, when the content expresses by base64, remove line break simply. Otherwise, replace line break with white space. | name | input | result | remarks | | - | - | - | - | | keywords without white space | 123<br>45<br>6 | 123 45 6 | Replace with white space | | keywords with white space | 123<br>45 6 | 123 45 6 | Replace with white space | | url without white space | http://exam<br>ple.<br>com | http://example.com | Remove line breaks | | url with white space | http://exam<br>ple.co m | http://example.co m | Remove line breaks | | data url without white space | data:text/html,123<br>45<br>6 | data:text/html,123 45 6 |Replace with white space | | data url with white space | data:text/html,123<br>45 6 | data:text/html,123 45 6 |Replace with white space | | base64 data url without white space | data:text/html;base64,123<br>45<br>6 | data:text/html;base64,123456 | Remove line breaks | | base64 data url with white space | data:text/html;base64,123<br>45 6 | data:text/html;base64,12345 6 | Remove line breaks | I will implement as above, but if you have opinions, please let me know.