Loading ...
Sorry, an error occurred while loading the content.

Re: [ydn-javascript] Re: [BUG] YAHOO.util.Dom.getXY returns 5 different results in 5 browsers

Expand Messages
  • Matt Sweeney
    Hi Iliyan, ... The workaround is to manually account for borderTop/Left widths up the ancestor axis of the node in FF2. Matt
    Message 1 of 6 , Jun 30, 2008
    • 0 Attachment
      Hi Iliyan,

      > So, it is working OK in all browsers, except FF2, probably due to
      > these border positioning issues you mentioned above. Are there some
      > workarounds for that?
      The workaround is to manually account for borderTop/Left widths up the
      ancestor axis of the node in FF2.

      Matt

      peychevi wrote:
      > --- In ydn-javascript@yahoogroups.com, Matt Sweeney <msweeney@...> wrote:
      >
      >> Hi,
      >>
      >>
      >>> Do you know why there are differences and how to fix this issue?
      >>>
      >> In some positioning contexts, borders in FF2 are known to skew
      >> positioning values.
      >>
      >> Have you tried using Dom.setXY to set the position? Using Dom.setXY
      >> will be more accurate x-browser than feeding Dom.getXY values to
      >> style.top/left.
      >>
      >
      > I have tried this, but in FF2 there were still some issues. FF3 hasn't
      > been released yet and I haven't tested with IE.
      >
      > Now I did it again and here are the results:
      > This fixed the issue in Internet Explorer, in FF2 it didn't.
      >
      > So, it is working OK in all browsers, except FF2, probably due to
      > these border positioning issues you mentioned above. Are there some
      > workarounds for that?
      >
      > Thank you very much!
      >
      >
      >> Matt
      >>
      >
      > Iliyan
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.