Context Navigation

Changes between Initial Version and Version 1 of Ticket #7224, comment 12

initial	v1
1	1	I still don’t see any reason for this. If someone wants to know if an object is a jQuery object, the standard mechanism for performing such a test is to inspect whether or not a jquery property exists, and that’s not likely to change any time soon since it is used very heavily internally and has been promoted as the de facto mechanism for testing.
2	2
3		Making this change only guarantees that people will end up assuming that its return value is a guarantee, when internally we are just doing the exact same thing. Additionally, this mechanism is intended only to expose the class type of JavaScript natives, not user-created classes, and I think it’s a ~~dangerous road to go down by embellishing it with special magic for jQuery~~.
	3	Making this change only guarantees that people will end up assuming that its return value is a guarantee, when internally we are just doing the exact same thing. Additionally, this mechanism is intended only to expose the class type of JavaScript natives, not user-created classes, and I think it’s at worst dangerous, at best needless to embellish it with special magic for jQuery just because we can.