On Feb 13, 2:50 pm, Michael Geary <m...@mg.to> wrote: > On Sun, Feb 13, 2011 at 5:18 AM, The Desk Wide Web <w...@deskwide.net> wrote: > > > > > Thanks for the response. You'd think not, but in my case, if I did not > > store copies of the strings, I could not delete the object properties. > > Could possibly be some ExtJS weirdness where it's monkey-patched Object > > and/or delete > > > I don't think it is possible to monkey-patch the delete operator out of > > existence. (Is it?) > > I would bet money that there is either something you're not telling us, or > something you're misinterpreting. In fact, I know I'd win that bet, because > you haven't posted a test case that anyone can look at. Without that, we're > all reduced to guessing. > > Can you post a test case that demonstrates this behavior? Then we could > easily get to the bottom of it.
Well I tested it enough without src'ing any Ext libraries to prove that everybody else was right and I was wrong ;) I'll try it again within my ExtJS app at work tomorrow; then if I'm still experiencing it, I'll try to reproduce it in a barebones ExtJS situation. Thanks....G -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/jsmentors@jsmentors.com/ To search via a non-Google archive, visit here: http://www.mail-archive.com/jsmentors@googlegroups.com/ To unsubscribe from this group, send email to jsmentors+unsubscr...@googlegroups.com
