Bug Tracker

Changes between Version 1 and Version 2 of Ticket #8634, comment 3


Ignore:
Timestamp:
Mar 26, 2011, 8:06:37 PM (11 years ago)
Author:
timmywil
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8634, comment 3

    v1 v2  
    1 I've already explained twice why this is damaging to maintainability and security. As I said before in the pull request,, how would you know when the context does or does not have access to the jquery prototype? You either need to assume always, or never, to have it be maintainable and secure. Again, please provide a use case where the existing architecture is not adequate.  I haven't seen that yet.  Avoiding referencing the prototype does not seem like the proper solution to supporting plain objects. We already do that in other ways in other functions without an inconsistent context. And sometimes, we don't want to support plain objects, so please be more specific.
     1I think this hurts maintainability and security because how would you know when the context does or does not have access to the jquery prototype? You either need to assume always, or never, to have it be consistent. I am having trouble thinking of a use case where the existing architecture is not adequate.  Perhaps you could provide a code example.