Would this construction:
e._prototypeStorage = e._prototypeStorage || {}
fall afoul of the issue that Jason pointed out? Would IE bork the
assignment because the key wasn't in hash form and quoted?
It will work fine. I've not found any specific property name which will
require quotes
I've had many instances where a javascript block would work in modern
standards compliant browsers yet fail silently in IE until I put quotes in,
single or double.
Please, show any example of such code.
--
You received this message because you are subscribed to the Google Groups
Internet explorer doesn't like object definitions without quotes around
the names
Hmm... example from Prototype 1.7 sources:
Object.extend(methods, {
getStorage: getStorage,
store: store,
retrieve: retrieve
});
Quotes are required for properties matching reserved
On Aug 9, 2012, at 5:28 AM, Victor wrote:
It may fail because this code may overwrite element's properties (and in some
browsers like IE and Opera some attributes, mapped as element properties).
That's an excellent point.
E.g. $(someInput).store(name, foo).store(type, bar); Better will be
I agree that some code is not always written like that - but I've had many
instances where a javascript block would work in modern standards compliant
browsers yet fail silently in IE until I put quotes in, single or double.
Jason Westbrook | T: 313-799-3770 | jwestbr...@gmail.com
On Thu, Aug
I have a function that might need to run under 1.6 or 1.7, but I don't want to
branch my code horribly around store and retrieve. This seems to work:
if(typeof Element.store == 'undefined'){
Element.addMethods({
store: function(elm, k, v){
elm[k] = v;
},
retrieve:
Internet explorer doesn't like object definitions without quotes around the
names
if(typeof Element.store == 'undefined'){
Element.addMethods({
store: function(elm, k, v){
elm[k] = v;
},
retrieve: function(elm, k){
return (elm[k]);
}
});
}
Jason Westbrook | T:
