From: David Mark on 19 Mar 2010 11:22 Garrett Smith wrote: > David Mark wrote: >> David Mark wrote: >>> Garrett Smith wrote: >>>> David Mark wrote: >>>>> David Mark wrote: >>>>>> Garrett Smith wrote: >>>>>>> Eric Bednarz wrote: > > [snip a bunch of noise] > You truly are hopeless. You really should be following me ("cinsoft" on Twitter). Good luck with the FAQ. :)
From: Garrett Smith on 19 Mar 2010 12:35 David Mark wrote: > Garrett Smith wrote: >> David Mark wrote: >>> David Mark wrote: >>>> Garrett Smith wrote: >>>>> David Mark wrote: >>>>>> David Mark wrote: >>>>>>> Garrett Smith wrote: >>>>>>>> Eric Bednarz wrote: >> [snip a bunch of noise] >> > > You truly are hopeless. You really should be following me ("cinsoft" on > Twitter). Good luck with the FAQ. :) I don't have much interest in following someone who cannot explain the reason for his own code (but keep up the marketing and you're bound to get some fool who will). -- Garrett comp.lang.javascript FAQ: http://jibbering.com/faq/
From: David Mark on 19 Mar 2010 14:32 Garrett Smith wrote: > David Mark wrote: >> Garrett Smith wrote: >>> David Mark wrote: >>>> David Mark wrote: >>>>> Garrett Smith wrote: >>>>>> David Mark wrote: >>>>>>> David Mark wrote: >>>>>>>> Garrett Smith wrote: >>>>>>>>> Eric Bednarz wrote: >>> [snip a bunch of noise] >>> >> >> You truly are hopeless. You really should be following me ("cinsoft" on >> Twitter). Good luck with the FAQ. :) > I don't have much interest in following someone who cannot explain the > reason for his own code (but keep up the marketing and you're bound to > get some fool who will). Once again, you are blind. Good luck with that!
From: Garrett Smith on 19 Mar 2010 16:27 David Mark wrote: > Garrett Smith wrote: >> David Mark wrote: >>> Garrett Smith wrote: >>>> David Mark wrote: >>>>> David Mark wrote: >>>>>> Garrett Smith wrote: >>>>>>> David Mark wrote: >>>>>>>> David Mark wrote: >>>>>>>>> Garrett Smith wrote: >>>>>>>>>> Eric Bednarz wrote: >>>> [snip a bunch of noise] >>>> >>> You truly are hopeless. You really should be following me ("cinsoft" on >>> Twitter). Good luck with the FAQ. :) >> I don't have much interest in following someone who cannot explain the >> reason for his own code (but keep up the marketing and you're bound to >> get some fool who will). > > Once again, you are blind. Good luck with that! No, I am not blind. You posted a suggestion to use offsetLeft and offsetTop to check the work of setting top and left values. That sort of feature test cannot work reliably, as offsetTop being nonstandard features that define what would be the "expected" value. | And now for the cunning bit. Compare the new offsetLeft/Top property | values to the old. If they are the same, you "guessed" right. If | they are off, vive la difference! That test would be then expressed as `doesPositionStyleAffectOffset`. Now if there is a point to performing such test, it has not been stated by you nor by anyone else. If there is no point to that code, then I would suggest it's removal from wherever it exists. It does not seem to answer your proposed question: "How do I get the current left/top/right/bottom/height/width/etc. styles?" Nor am I hopeless. Annoyed, yes, a little annoyed. -- Garrett comp.lang.javascript FAQ: http://jibbering.com/faq/
From: David Mark on 19 Mar 2010 17:14
Garrett Smith wrote: > David Mark wrote: >> Garrett Smith wrote: >>> David Mark wrote: >>>> Garrett Smith wrote: >>>>> David Mark wrote: >>>>>> David Mark wrote: >>>>>>> Garrett Smith wrote: >>>>>>>> David Mark wrote: >>>>>>>>> David Mark wrote: >>>>>>>>>> Garrett Smith wrote: >>>>>>>>>>> Eric Bednarz wrote: >>>>> [snip a bunch of noise] >>>>> >>>> You truly are hopeless. You really should be following me >>>> ("cinsoft" on >>>> Twitter). Good luck with the FAQ. :) >>> I don't have much interest in following someone who cannot explain the >>> reason for his own code (but keep up the marketing and you're bound to >>> get some fool who will). >> >> Once again, you are blind. Good luck with that! > No, I am not blind. You've been acting like you can't see the forest for the trees with numerous suggestions of mine. It's been going on for years. > > You posted a suggestion to use offsetLeft and offsetTop to check the > work of setting top and left values. That sort of feature test cannot > work reliably, as offsetTop being nonstandard features that define what > would be the "expected" value. You still don't get it and I don't care. Dig a little deeper. Twitter has the links you need (or just visit my home page). ;) > > | And now for the cunning bit. Compare the new offsetLeft/Top property > | values to the old. If they are the same, you "guessed" right. If > | they are off, vive la difference! > > That test would be then expressed as `doesPositionStyleAffectOffset`. > Now if there is a point to performing such test, it has not been stated > by you nor by anyone else. Wrong. We've had this discussion more than once. I've all but spelled it out here. Now I have spelled it out (in code) on my site. > > If there is no point to that code, then I would suggest it's removal > from wherever it exists. You aren't in a position to suggest removing code you clearly don't understand. > > It does not seem to answer your proposed question: "How do I get the > current left/top/right/bottom/height/width/etc. styles?" Asked and answered. > > Nor am I hopeless. Annoyed, yes, a little annoyed. Join the club. Starting with isHostMethod, then viewport measurement and now this (and many in between). I'm tired of revisiting the same "arguments" over and over. |