On Tue, 9 Sep 2008, LarryK wrote:
snip
> ===>>> Hello fellow readers, has anyone else seen the problem that
> Mike is having? (See first post in this thread.)
>
> Regards,
>
> Larry

Yes. I posted a +1 on Aug. 1. I fixed it by hijacking the function 
SimileAjax.Graphics._FontRenderingContext.prototype.computeSize per 
David's suggestion of Jul. 28:

> If you look in
> http://static.simile.mit.edu/timeline/api-2.0/scripts/original-painte...
> and search for
>     this._frc.computeSize
> That's where those widths get measured. FRC stands for
> FontRenderingContext and is implemented at the end of
>     http://static.simile.mit.edu/ajax/api-2.0/scripts/graphics.js
> As a test, you could override
>     SimileAjax.Graphics._FontRenderingContext.prototype.computeSi
> and, say, add 5 to the returned width. That'd probably fix it, though
> that's fixing the symptom than the cause.

As he suggested, this fixed the symptom. You can see a comparison here:

This calls a js page JohnItinerary.js with the above fix implemented:
http://home.myuw.net/jjcrump/Timelines/itinerary/JohnItinerary.html and 
it's rendered correctly in both safari and FF.

This:
http://home.myuw.net/jjcrump/Timelines/itinerary/FFwrappingTest.html
calls the js at FFwrappingTest.js with the hijacked function commented 
out. Safari 3.1.2 renders the event labels correctly, FF 3.0.1 wraps them.

Note that these pages are calling the static timeline 2.0 api at 
http://static.simile.mit.edu/timeline/api-2.0/timeline-api.js

Allow me to add my 'me too' again, in the hope that someone with deeper 
browser knowledge will know how to file the bug with FF if that's where 
the problem lies.

Jon
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to