Re: YAHOO.util.Dom.getXY returns 5 different results in 5 browsers

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:
&gt; --- In ydn-javascript%40yahoogroups.com">ydn-javascriptyahoogroups.com, Matt Sweeney <msweeney...> wrote:
&gt;
>>; Hi,
>>
>>
>>;> Do you know why there are differences and how to fix this issue?
&gt;>>
>>; 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
&gt; 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?
&gt;
> Thank you very much!
&gt;
>
>>; Matt
>;>
>
> Iliyan
&gt;
>
>

Messages in this topic (6) Reply (via web post) | Start a new topic

.