Hi,
Thanks for your reply. I hadn't been thinking along the lines of doctypes,
but went ahead and tried a bunch of different flavors. None worked, but
along the way I found a great web site that demystifies the topic:
http://hsivonen.iki.fi/doctype/
I do know that the incoming xml file is getting parsed correctly and that
the DefaultEventSource.Event.getLink() function returns the correct event
link. So now I'm working on the hypothesis that the listener is not getting
instansiated correctly because an alert set at
Timeline.OriginalEventPainter.prototype.addOnSelectListener =
function(listener) {
alert ("eventListener instansiated");
this._onSelectListeners.push(listener);
...doesn't get triggered.
I'll share whatever solution/workaround I find. Meanwhile, if you have any
further inspirations you'd care to share, I'm all ears.
Best,
- pat
On Wed, Apr 8, 2009 at 3:57 PM, Stefano Mazzocchi <[email protected]>wrote:
>
> P.J. Barton wrote:
> > Hi,
> >
> > I'm encountering a strange bundle of issues rendering timeplots with
> > event overlays that occur only in IE but never in FF.
> >
> > Within either FF or IE, (with showValues set to true in the
> > Timeplot.createPlotInfo() spec). Timeplot works perfectly. I can
> > gracefully drag my mouse over a timeplot and see the data in the
> > mouse-over pop-up windows.
> > So far, so good.
> >
> > With the addition of an event, including a link property the behavior is
> > very different. FF behaves as expected. With the mouse positioned over
> > the region covered by the event, the mouse-over pop-ups show up and the
> > cursor changes to let me know there's a link.
> >
> > However in IE, with the mouse over the region covered by the event, the
> > mouse-over popups show up at the "beginning of time". In other words,
> > they would be in the right place and contain the appropriate data *but
> > only if* the event started at the first date of the whole timeplot (it
> > doesn't). And the cursor doesn't change to indicate a link.
> >
> > It's as though the mouse over triggers the right event, using the right
> > index, but on the wrong object.
> >
> > Neither FF nor IE show any browser/js errors.
> >
> > I'm wondering if anyone else has run into this phenomenon?
>
> hmmm, smells of standard vs. quirks mode problems. have you tried
> changing DOCTYPE declarations in your HTML pages?
>
> --
> Stefano Mazzocchi Application Catalyst
> Metaweb Technologies, Inc. [email protected]
> -------------------------------------------------------------------
>
>
> >
>
--
Patrick J. Barton
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
