2015-11-30 05:04:13 |
Aaron Wells |
description |
Robert noticed that there is a merge conflict ">>>>>" line left over in tinymce.jquery.js. It was apparently introduced in commit 3db4ecaf, one of the bootstrap commits. The merge conflict was later partially cleaned up in commit e0d6f1c67f8ac, but this part was overlooked.
Looking closer, it's also apparent that quite a bit of duplicated code from that merge conflict was also left in place. |
Robert noticed that there is a merge conflict ">>>>>" line left over in tinymce.jquery.js. It was apparently introduced in commit 3db4ecaf, one of the bootstrap commits. The merge conflict was later partially cleaned up in commit e0d6f1c67f8ac, but this part was overlooked.
Looking closer, it's also apparent that quite a bit of duplicated code from that merge conflict was also left in place.
It's unclear whether this has caused any bugs, or which section of TinyMCE would cause this code to be executed. |
|
2015-11-30 05:05:52 |
Aaron Wells |
description |
Robert noticed that there is a merge conflict ">>>>>" line left over in tinymce.jquery.js. It was apparently introduced in commit 3db4ecaf, one of the bootstrap commits. The merge conflict was later partially cleaned up in commit e0d6f1c67f8ac, but this part was overlooked.
Looking closer, it's also apparent that quite a bit of duplicated code from that merge conflict was also left in place.
It's unclear whether this has caused any bugs, or which section of TinyMCE would cause this code to be executed. |
Robert noticed that there is a merge conflict ">>>>>" line left over in tinymce.jquery.js. It was apparently introduced in commit 5ba3418499cc419e, one of the bootstrap commits. The merge conflict was later partially cleaned up in commit e0d6f1c67f8ac, but this part was overlooked.
Looking closer, it's also apparent that quite a bit of duplicated code from that merge conflict was also left in place.
It's unclear whether this has caused any bugs, or which section of TinyMCE would cause this code to be executed. |
|