[jquery-dev] Re: jQuery forward compatibility issues

2010-01-05 Thread dotnetCarpenter
Same issue with css property clip from CSS2.. http://www.w3.org/TR/CSS21/visufx.html#clipping -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group,

Re: [jquery-dev] Re: jQuery forward compatibility issues

2009-11-23 Thread Mike Taylor
I just wanted to point out that the problem described for text-shadow can be a lot more complicated than animating 4 different values, e.g.: text-shadow: 1px 1px 3px #666, -1px -1px 3px #FFF, 1px 1px #666, -1px -1px #FFF; So here you have 14 values. Also, box-shadow was removed from the CSS3 spe

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-20 Thread Dave Methvin
fantasai suggested I post the proposal in the public mailing list, which I did this evening: http://lists.w3.org/Archives/Public/www-style/2009Nov/0279.html -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-20 Thread dotnetCarpenter
It was late last night when I wrote the names of the spec authors. It should have been only Elika and Paul Nelson (paulnel at microsoft.com). The other authors was from the CSS Background and Borders Module. I just sent an e-mail to Elika. Hi Elika. I've looked into some of the new CSS3 additions

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-20 Thread Dave Methvin
> ^_^ Now you need: > opacity: .5; -ms-filter: > "progid:DXImageTransform.Microsoft.Alpha(Opacity=50)"; filter: > progid:DXImageTransform.Microsoft.Alpha(Opacity=50); zoom: 1; And even with all that, IE's fauxpacity still interacts poorly with other Microsoft features like ClearType. -- You rece

Re: [jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread Daniel Friesen
dotnetCarpenter wrote: > ... > It's actually fun to think that even thought IE rightly deserve a lot > bashing for stopping browser innovation, it was the first browser to > support image transparency, persistent storage, gradient ect. haha! > ^_^ And then you look at what they did in ie8 to all

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread Dave Methvin
> When you have a CSS property that has not been implemented in a pattern > similar to other long-standing properties (e.g. text-shadow-radius), it > seems that animating such a combined property would fall under an edge case > requiring custom code. Yeah, I hadn't looked at these CSS3 additions

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread dotnetCarpenter
> Well if it won't be a problem until IE9 comes out, we have a couple of > years. :-) text-shadow is possible in all browsers right now (using filters, IE was actually the first browser to implement this in the 90's) but I figure that people won't complain about it until IE9 is out and designers be

RE: [jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread Jeffrey Kretz
would be fully functional in the current codebase with no modifications. JK -Original Message- From: dotnetCarpenter [mailto:jon.ronnenb...@gmail.com] Sent: Thursday, November 19, 2009 1:54 PM To: jQuery Development Subject: [jquery-dev] Re: jQuery forward compatibility issues You're de

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread dotnetCarpenter
> jQuery should either embrace these new > property syntaxes or put pressure on the CSS spec authors to change it > to the ol' fashion way. Apparently Elika J. Etemad is the guy to ask about changing the specs. At least it says so over at the current work page from w3c http://www.w3.org/Style/CSS/c

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread Dave Methvin
Well if it won't be a problem until IE9 comes out, we have a couple of years. :-) BTW, according to the pages you referenced, those args are out of order. The color is supposed to come last. -- You received this message because you are subscribed to the Google Groups "jQuery Development" group.

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread dotnetCarpenter
You're dead-on Dave. The same problem arise with box-shadow and possibly other features. jQuery should either embrace these new property syntaxes or put pressure on the CSS spec authors to change it to the ol' fashion way. I don't know what is most appropriate but this will soon be a real pain when

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread Dave Methvin
> To my surprise the css method with name/value does actually work. It's just assigning a string value to a css property, so it should work. > But as stated in my first post, animate fails I want to be sure I understand what animate was expected to do. So you wanted animate to change the text-sh

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread dotnetCarpenter
Sorry, there is a bug in the compiled code (blame http://closure-compiler.appspot.com/home). This should work: (function(d){function f(a){var b=a.css("display"),c=a.css ("display","inline").width();a.css("display",b);return 80+a.position ().left+c}function e(a,b,c){return{style:"left:-"+a +"px;po

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-19 Thread dotnetCarpenter
I've only tested in FF3.5, Chrome 3.0 and Safari 4 as they are the only browsers that I'm aware of supports text-shadow. You can test it yourself with this code (uncomment in appropriate order): jQuery(function($){ // test that text-shadow is supported - always work //

[jquery-dev] Re: jQuery forward compatibility issues

2009-11-18 Thread Dave Methvin
> jQuery doesn't support CSS properties with multiple > arguments like text-shadow. What goes wrong, in particular, and on which browsers? Is it a problem with the setter, the getter, or both? -- You received this message because you are subscribed to the Google Groups "jQuery Development" grou