On May 14, 2009, at 5:39 AM, Olemis Lang wrote:
> > On Thu, May 14, 2009 at 12:17 AM, Noah Kantrowitz > <[email protected]> wrote: >> On May 13, 2009, at 8:25 AM, Olemis Lang wrote: >>> >>> Hello Noah ... Once again. >>> >>> You were definitely right: My version was not updated. I really see >>> some improvements in the latest one; >>> >>> However : >>> >>> 1. There is another issue now with carousel. >> >> Yeah, seemed to be a bug in the carosel code that I didn't feel like >> bothering. The right arrow behaves as it should and loops around. >> > > its no big deal ... really ;) > >>> 2. The same non-portable JS code is already there. It breaks the >>> UI in Firefox and Opera, and «possibly» >>> Chrome (i.e. real browsers :P ... and I'm not saying that >>> anybody >>> has included non-portable code, and non-standard features in >>> browsers :$ ... I'm not even mentioning wich one ... did I ? ;) >> >> Which JS is that? I don't have opera, but I tested everything in IE7, >> Fx3, and Safari. > > Well I tested it in Firefox, Opera & MS IE and the only one that works > is the later. In Firefox 3.x & Opera 9.x it gets broken since it seems > that JS global variable named `console` is missing . AFAICR I made > other minor changes too. Ahh, console is an object added by Firebug, the only things it would break are logging, which is fine. > > >> The dynamic rules stuff in the scheme builder is >> definitely far from simple, so not working in Opera wouldn't shock me >> too much. > > JFYI: I often read this book named -more or less- Complete CSS > Reference (Sitepoint) and after reading a little yesterday it is > obvious why std features in CSS -and JS [3]_ it's obvious ! - dont > work in MS IE, and why non-std features work in MS IE . MS doesnt > respect stds . Almost the entier book is dedicated to explain why MS > IE doesnt work -it's obviously broken-, and when it «seems» to work, > why the implementation is buggy. In fact they refer to MS model saying > it is the «Internet Explorer box model bug» [1]_ [2]_ and, since > somebody says they fixed it, they even have to explain why they didnt. > > Safari, Ffx & Opera support much more features, and sometimes only one > of them is the only one that supports parts of the CSS std. The same > happens with JS . Everybody -specially MS IE- is doing things the way > they want to, and it seems MS doesnt want to know about web stds ... > but anyway, that's their own business, and even if many like me are > affected due to those «practices», there's nothing we can do about > that > MS rants aside, IE actually implements the rule API quite well, just via two non-standard function names. Within themeengine that is hidden behind a jquery plugin anyway. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
