We break FCKeditor fairly often. How about making it part of our automated tests? http://www.fckeditor.net/license http://dev.fckeditor.net/wiki/Testing
This would be some good automated testing considering recent bug 453462 and all the others times this happenned... Fckeditor is widly used.
Fixed by + flag in bug 453462
Depends on: 453462
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
That doesn't fix this. All that did was add one test for one specific case that we broke. Actually adding FCKeditor's testsuite would ensure that we don't break anything that FCKeditor uses, which was Jesse's point in comment 0.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This sound like a good idea!
Summary: Consider integrating FCKeditor test suite → Integrate FCKeditor test suite
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.