Hi Jon, Thanks for your time on this.
Re: > As you can see from the screenshots, not all of the event labels are > incorrectly wrapped. It's not clear to me why most are wrapped, but some > are not. I'm not sure how I might frame this as a bug report to the FF > people. > Tricky....good news is that I now have access to a Mac with FF3.0.1 and I can now see the problem too. I brought up the JFK example on the mac and it is quite interesting how some of the labels wrap and others don't Unfortunately, I don't have the time right now to investigate this further (it's certainly on my list but other items are higher.) ==>> Could you investigate creating a minimal timeline example html that demonstrates the wrapping problem on a Mac? Eg, no Google map, no background, just a couple of events, etc. I'll then use it in a bug report to the Firefox people. In addition, it will help me try and figure out the issue here. Thank you for any time you can put into this. Re: > By the way, I'm pleased to see some knowledgeable folks picking up the > torch on this API. I appreciate your scroll-wheel contribution. You may be > interested to know that the examples you're serving from your own site > work fine when I'm using a mouse. Thanks! I appreciate your testing, help and time too. > Here's an interesting bug however: I > have my MacBook set to use the two fingered gesture to scroll (hmm, that > might read a little differently in the UK ;-) ). When I do that, I get the > default behavior, scroll the window, AND scroll the timeline at the same > time. Weird. Interesting. Sounds like the scroll events initiated by the gesture are not being canceled in the Timeline handler. The event is canceled near the end of function Timeline._Band.prototype._onMouseScroll in file src\webapp\scripts\timeline.js look for the comment "prevent bubble" The Mac I have ready access to does not have a touchpad (it's a desktop), so I can't test the problem. I have added your comment to the Wiki mouse-wheel page. ==>> Does it happen in both the FF and Safari browsers on the Mac? Or just Safari? > > Kudos all on the continued development; I look forward to more. I wonder > if you, or someone, would clarify the future course of timeline. Is http://static.simile.mit.edu/timeline/api-2.0/timeline-api.js now frozen, > or will the new changes be committed to it at some future date; or, is > such a decision tabled until the outcome of discussions with google about > hosting the api? Allow me to get very specific for a moment: The .../api-2.0/... library on MIT, http://static.simile.mit.edu/timeline/api-2.0/timeline-api.js should NEVER change since any changes might effect some pages that make use of those files. Once we have a 2.1.0 (and later releases), the question will be "will api-2.1.0 be available from the MIT server or elsewhere? (on url .../api-2.1.0/...)" afaik, at this point, the question is tabled until David H hears back from Google. I'll be meeting with a contact at a large internet company on the 18th, that will be another possible hosting option. Regards, Larry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
