Re: Issue 953 in google-caja: Subjective vs Record inheritance

[googl...@googlecode.com]

Updates:
Status: Postponed

Comment #7 on issue 953 by erights: Subjective vs Record inheritance
http://code.google.com/p/google-caja/issues/detail?id=953

(No comment was entered for this change.)

[googl...@googlecode.com]

Updates:
Status: Fixed

Comment #8 on issue 953 by eri...@google.com: Subjective vs Record
inheritance
http://code.google.com/p/google-caja/issues/detail?id=953

This thorn in our side is now fixed, as expected, by ES5/3. I can't test
the "push" example code above because the current property virtualization
prevents tamed primordial methods from being deleted. Once we transition to
objective replacement, I'll be able to test this case as well.

[googl...@googlecode.com]

Comment #9 on issue 953 by michaelj...@gmail.com: Subjective vs Record
inheritance
http://code.google.com/p/google-caja/issues/detail?id=953

Then shouldn't this issue remain open until that push example is both
testable and working? We don't want this forgotten about just so we can
have less tickets open, right?

[googl...@googlecode.com]

Updates:
Status: Postponed

Comment #10 on issue 953 by eri...@google.com: Subjective vs Record
inheritance
http://code.google.com/p/google-caja/issues/detail?id=953

Good point. Reverting to Postponed.

[googl...@googlecode.com]

Updates:
Status: WontFix

Comment #11 on issue 953 by metaw...@gmail.com: Subjective vs Record
inheritance
http://code.google.com/p/google-caja/issues/detail?id=953

We're not going to move away from virtualization in ES5/3.