Details
Improvement
Major
Description
Our JavaScript bridge relies on the Prototype JavaScript library and extends the native JavaScript Object with our own utility functions. We've run into a problem in a couple of separate instances where other JS code is run (typically in some sort of loop or iteration) and the logic of the loop does NOT take into consideration that the functions we've bound to the top-level Object. In these cases, the behaviour gets unpredictable and cause the JS code to fail.
There is some debate online whether what we are doing is "rude" or not a best practice. Putting that debate aside, it's likely that this will cause a number of problems for us and our customers in the future and we should look at doing this in a different way.
There is some debate online whether what we are doing is "rude" or not a best practice. Putting that debate aside, it's likely that this will cause a number of problems for us and our customers in the future and we should look at doing this in a different way.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #14640 | Mon Aug 13 11:53:13 MDT 2007 | mircea.toma | Remove custom Object.prototype methods -- |
| Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/bridge/lib/enumerator.js
MODIFY
/icefaces/trunk/icefaces/bridge/lib/event.js
MODIFY
/icefaces/trunk/icefaces/bridge/lib/parameters.js
MODIFY
/icefaces/trunk/icefaces/bridge/src/submit.js
|