Hi Patrick, Good sleuthing!
I looked at the MS bug report. ==>> I think their suggested fix of using outerHTML instead of removeChild is NOT something that we'd want to do in Timeline. removeChild is much more standard and faster than outerHTML . The bug report says that moving background images to the css file will also avoid triggering the IE bug. I think moving images to the CSS file sounds reasonable if it does the trick. It also says that this particular bug only happens if divs have a background image. I suggest that the first verification would be to remove all background images and still see if the bug occurs. Regards, Larry On Oct 3, 7:00 pm, Patrick <[EMAIL PROTECTED]> wrote: > So the issue is removeChild. If you reference this > page:http://support.microsoft.com/kb/925014 > > Here you will find an explanation from M$ that removeChild on a div > element that has a background-url set will cause IE to say the page > has insecure and secure content. I started digging through the code > and removeChild is used alll over the place. Now these locations might > not fit all of the criteria described in that article, but there are > some that do somewhere in the code. This is going to require a pretty > big change in the code. Also jcorreia the function that you are > calling in your code is not Timeline.loadJSON but actually > > Timeline.DefaultEventSource.prototype.loadJSON = function(data, url) { > var base = this._getBaseURL(url); > var added = false; > if (data && data.events){ > var wikiURL = ("wikiURL" in data) ? data.wikiURL : null; > var wikiSection = ("wikiSection" in data) ? data.wikiSection : > null; > > var dateTimeFormat = ("dateTimeFormat" in data) ? > data.dateTimeFormat : null; > var parseDateTimeFunction = > this._events.getUnit().getParser(dateTimeFormat); > > for (var i=0; i < data.events.length; i++){ > var event = data.events[i]; > var evt = new Timeline.DefaultEventSource.Event( > ("id" in event) ? event.id : undefined, > parseDateTimeFunction(event.start), > parseDateTimeFunction(event.end), > parseDateTimeFunction(event.latestStart), > parseDateTimeFunction(event.earliestEnd), > event.isDuration || false, > event.title, > event.description, > this._resolveRelativeURL(event.image, base), > this._resolveRelativeURL(event.link, base), > this._resolveRelativeURL(event.icon, base), > event.color, > event.textColor, > event.classname > ); > evt._obj = event; > evt.getProperty = function(name) { > return this._obj[name]; > }; > evt.setWikiInfo(wikiURL, wikiSection); > > this._events.add(evt); > added = true; > } > } > > if (added) { > this._fire("onAddMany", []); > } > > }; > > The solution might be writting this out to a file and loading it. This > is a terrible way to do it, and it may be my temporary fix. > > On Sep 11, 2:01 pm, jcorreia <[EMAIL PROTECTED]> wrote: > > > Thanks, > > but I have been there and checked that. > > I´m using version 2.0 and the paths are well built with > > 'SimileAjax.urlPrefix' and the problem is indeed the loadJson method. > > I need a fix or a way to load the data without going to search for an > > url, since I´ve got all the json I need ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
