[mochikit] Re: Calling the rounding function after the page has loaded

2006-12-20 Thread Andrew
I did some further testing. I seem to be getting a border rendering issue with this test example in both Firefox 2 and IE --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send

[mochikit] Re: Calling the rounding function after the page has loaded

2006-12-14 Thread Thomas Hervé
The first problem I see is that you call roundClass with the option border at true, whereas it takes a color as argument. It should be in the documentation though. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

[mochikit] Re: Calling the rounding function after the page has loaded

2006-12-14 Thread [EMAIL PROTECTED]
Thomas Hervé wrote: The first problem I see is that you call roundClass with the option border at true, whereas it takes a color as argument. It should be in the documentation though. No, the documentation says that the default value for border is false. That would indicate it is a boolean

[mochikit] Re: Calling the rounding function after the page has loaded

2006-12-14 Thread Thomas Hervé
[EMAIL PROTECTED] a écrit : Thomas Hervé wrote: The first problem I see is that you call roundClass with the option border at true, whereas it takes a color as argument. It should be in the documentation though. No, the documentation says that the default value for border is false.

[mochikit] Re: Calling the rounding function after the page has loaded

2006-12-14 Thread Andrew
Thanks for the border solution. I changed the border from false to an rgb() or hex value. I still have problems with FF2's white corners and some borders that the script generates in IE6 are messed up. Is this my css is it rendering incorrectly?

[mochikit] Re: Calling the rounding function after the page has loaded

2006-12-13 Thread Bob Ippolito
The problem would probably be tracked down and fixed faster if you provided a full, runnable, example that simply reproduces the problem. -bob On 12/13/06, Andrew [EMAIL PROTECTED] wrote: I had to put try and error catching in _createCornerSlice: function to get IE 6 stopping because of an