It seems that both of them could make the element move from its current position. Are these two methods interchangeable?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It seems that both of them could make the element move from its current position. Are these two methods interchangeable?
The two methods are not exactly the same thing: Translating an element will not require to change its
top,left,rightorbottomCSS properties, so in the same wayoffsetTop/offseLeftJavascript properties are not affected by a CSS translation. Beside, the position of the element could be alsostatic(and thus noz-indexis required)If you use
position: relativeinstead, you will change those properties to visually achieve the same effect.Example Fiddle: http://jsfiddle.net/LkLey/
Of course if you have to deal with old browser (like
IE8orFF2) the necessary choice is relative positioning, otherwise I can’t see a clear convenience on choosing one of the two methods (well, to be honest relative positioning has no need of multipe prefixes-moz-,-webkit-… to work everywhere) so the choice is up to you (and it depends on the layout).