javascript - General reasons not to deal with Document's and Element's prototype -


are there general reasons not deal document's , element's prototype?

i create own little framework, because current project doesn't need mass of features of existing frameworks.

i don't need support browsers don't support element/document-constructor , not execute scripts not under control.

so recommend extend prototype or should go usual way , create own objects element/document?

do plan extend default dom elements? if so, please don't. juriy zaytsev (aka kangax) describes why not in what’s wrong extending dom.


Comments

Popular posts from this blog

ruby - When to use an ORM (Sequel, Datamapper, AR, etc.) vs. pure SQL for querying -

php - PHPDoc: @return void necessary? -

c++ - Convert big endian to little endian when reading from a binary file -