Native Objects"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(New page: The V3 code should completely avoid extending native JavaScript objects, like String or Array. This is already a big problem we see out there (e.g. Prototype), having "collisions" when put...)
 
(No difference)

Latest revision as of 11:39, 15 March 2008

The V3 code should completely avoid extending native JavaScript objects, like String or Array. This is already a big problem we see out there (e.g. Prototype), having "collisions" when putting different libraries to run together.

Our code must also consider the fact that native objects may have been modified by external libraries, so we should not rely on having "pure" native objects.

This page was last edited on 15 March 2008, at 11:39.