Skip to main content

CSS3 transitions inconsistent across FF and Chrome



So I have created a CSS3 animation that does not behave consistently across the different browsers. Here is a quick and dirty overview, and I have included a JSFiddle link at the end.





Here is the CSS:







.cloned_object {

position:absolute;

background-color:white;

width: 700px;

height: 640px;

margin: 0; /*for centering purposes*/

-webkit-transition: width 1s, height 1s, top 1s, left 1s, margin 1s;

-moz-transition: width 1s, height 1s, top 1s, left 1s, margin 1s;

-ms-transition: width 1s, height 1s, top 1s, left 1s, margin 1s ;

transition: width 1s, height 1s, top 1s, left 1s, margin 1s;







}





and the JS function:







$('.content_cell').on('click', function(event) {

// if the user is on a browser older then IE9

if ($.browser.msie && $.browser.version.substr(0,1)<10) {

var $clonedElement = $( this ).clone(true).attr('class','cloned_object content_cell').appendTo('#mainContentTable');

$clonedElement.css({left:$(this).position().left,

top:$(this).position().top,

opacity:1.0}) ;



selectedPos = $(this).position();



var currentPos = $('#invitedToChatCell').position();



$clonedElement.animate({

height:640, width:700,

//position:'absolute',

left:currentPos.left,

top:currentPos.top,

opacity:1.0

}, 500, function(){ $('.cloned_object > ul').toggle(); });



} else {

var currentPos = $('#invitedToChatCell').position();



var $clonedElement = $( this ).clone(true).attr('class', 'content_cell').appendTo('#mainContentTable');

$clonedElement.css({left:$(this).position().left,

top:$(this).position().top}) ;



$clonedElement.addClass('cloned_object');

$clonedElement.css({'margin-left':-$(this).position().left+125,

'margin-top':-$(this).position().top,

}) ;



selectedPos = $(this).position();



$('.cloned_object > ul').toggle();

}



event.stopPropagation();

});







I am really at a loss as to why it would be different across browsers. I was hoping someone could enlighten me as to what is going on...





HERE IS THE JSFIDDLE LINK If you run it in both browsers, you will see the animation position is different. In FF, it looks like the box grows, that is what I want. In chrome it's very strange...


Comments

  1. Your transitions explicitly request that the "top" and "left" be animated. They've got to start from somewhere, so they start from zero. It's a weird case because the "cloned-element" style is not what's giving the element the "top" and "left" values, it's your code which puts them straight on the element.

    You're also animating the margin, however; Chrome doesn't seem to pay much attention to that. If I take the "top" and "left" properties out of the transition, it makes it act a little more like Firefox.

    The concept of applying a transition to an element at the same time it comes into existence is a little confusing to me. I hope somebody comes along and provides a better answer.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex