Rails spinoffs - Aug 2006 - Autocompleter positions div in wrong place

Hi-

I am having trouble with the Autocompleter in which the autocomplete
box appears in the wrong place (above and to the left of the text box).
 This only seems to be a problem in Firefox and is caused by
Position.clone function setting an incorrect position for the target
(the autocomplete box).  From what I can tell, the parent that it finds
for the target is incorrect.  My problem seems to be related to the
Autocompleter being the child of a <td>.  Does anyone have any thoughts
on this?  Seen a similar probelms?

Thanks!


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Please disregard my question below.  After running through the
Javascript some more, I found that it searches for the target
element''s parent until it reaches the body tag or a parent with
non-static positioning.  In reviewing my HTML and CSS, I found a
parent element that had absolute positioning, thus causing my problem.
 Firefox handles positioning different than IE, hence the incorrect
placement of my autocompleter.

Thanks.

On 8/29/06, Josh <joshua.a.kahn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Hi-
>
> I am having trouble with the Autocompleter in which the autocomplete
> box appears in the wrong place (above and to the left of the text box).
>  This only seems to be a problem in Firefox and is caused by
> Position.clone function setting an incorrect position for the target
> (the autocomplete box).  From what I can tell, the parent that it finds
> for the target is incorrect.  My problem seems to be related to the
> Autocompleter being the child of a <td>.  Does anyone have any
thoughts
> on this?  Seen a similar probelms?
>
> Thanks!
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Hi,

Actually Firefox'' behavior is the correct one.

You will, however, find a similar issue on Opera9, which is my problem
just now.

When there''s no positioned container to the text input, it will display
the completions at (0,0) of the body (+ body margins).

If there is a positioned container, it will display at proper top
offset, but still at zero left offset.

I put a reproducible case online:
http://www.tddsworld.com/bugs/autocompleter_opera9_issue/index.html

It doesn''t use any positioned container. This very page works fine on
MSIE 6, Firefox 1.5 and Konqueror 3.5.2. I haven''t got Safari feedback
yet.

Position.clone, which is Prototype stuff, does seem to be the culprit
here, but I need a solution quick. Those willing to tinker with this
code can find a ZIP file on the online demo''s parent directory.

Thanks in advance all,

-- 
Christophe Porteneuve


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Works on Safari 2, but it also submits the form (iirc, that''s something
we tried fixing on Safari, but somehow it didn''t work out).

-Thomas

Am 01.09.2006 um 11:57 schrieb Christophe Porteneuve:
>
> Hi,
>
> Actually Firefox'' behavior is the correct one.
>
> You will, however, find a similar issue on Opera9, which is my problem
> just now.
>
> When there''s no positioned container to the text input, it will  
> display
> the completions at (0,0) of the body (+ body margins).
>
> If there is a positioned container, it will display at proper top
> offset, but still at zero left offset.
>
> I put a reproducible case online:
> http://www.tddsworld.com/bugs/autocompleter_opera9_issue/index.html
>
> It doesn''t use any positioned container. This very page works fine
on
> MSIE 6, Firefox 1.5 and Konqueror 3.5.2. I haven''t got Safari
feedback
> yet.
>
> Position.clone, which is Prototype stuff, does seem to be the culprit
> here, but I need a solution quick. Those willing to tinker with this
> code can find a ZIP file on the online demo''s parent directory.
>
> Thanks in advance all,
>
> -- 
> Christophe Porteneuve
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Please find my correction on this patch :

http://dev.rubyonrails.org/ticket/5848


Christophe Porteneuve wrote:
> Hi,
>
> Actually Firefox'' behavior is the correct one.
>
> You will, however, find a similar issue on Opera9, which is my problem
> just now.
>
> When there''s no positioned container to the text input, it will
display
> the completions at (0,0) of the body (+ body margins).
>
> If there is a positioned container, it will display at proper top
> offset, but still at zero left offset.
>
> I put a reproducible case online:
> http://www.tddsworld.com/bugs/autocompleter_opera9_issue/index.html
>
> It doesn''t use any positioned container. This very page works fine
on
> MSIE 6, Firefox 1.5 and Konqueror 3.5.2. I haven''t got Safari
feedback
> yet.
>
> Position.clone, which is Prototype stuff, does seem to be the culprit
> here, but I need a solution quick. Those willing to tinker with this
> code can find a ZIP file on the online demo''s parent directory.
> 
> Thanks in advance all,
> 
> -- 
> Christophe Porteneuve

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Hello,

ogarbe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> Please find my correction on this patch :
>
> http://dev.rubyonrails.org/ticket/5848
Alright. Looking at your patch, I see that:

a) You don''t want Opera to clone pos at completion time, you want it
early on. Why?
b) You align offsetLeft on the element''s *offsetWidth*. How come?

Looking forward to your answers,


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Christophe Porteneuve wrote:
> Hello,
>
> ogarbe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> > Please find my correction on this patch :
> >
> > http://dev.rubyonrails.org/ticket/5848
>
> Alright. Looking at your patch, I see that:
>
> a) You don''t want Opera to clone pos at completion time, you want
it
> early on. Why?
> b) You align offsetLeft on the element''s *offsetWidth*. How come?
>
> Looking forward to your answers
in fact, I don''t really know why, I tried a lot of things for this
autocompleter problem and found this solution. Sorry :)


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Hi Thomas,

the prototype Element.observe function changes keypress observing to  
keydown observing on Safari, i think because of the strange keyCodes  
delivered by keypress events in Safari.
Safari cancels submission on keypress events, but not on keydown events.

Regards,

Lorenz


On 01.09.2006, at 19:11, Thomas Fuchs wrote:
>
> Works on Safari 2, but it also submits the form (iirc, that''s  
> something
> we tried fixing on Safari, but somehow it didn''t work out).
>
> -Thomas
>
> Am 01.09.2006 um 11:57 schrieb Christophe Porteneuve:
>
>>
>> Hi,
>>
>> Actually Firefox'' behavior is the correct one.
>>
>> You will, however, find a similar issue on Opera9, which is my  
>> problem
>> just now.
>>
>> When there''s no positioned container to the text input, it
will
>> display
>> the completions at (0,0) of the body (+ body margins).
>>
>> If there is a positioned container, it will display at proper top
>> offset, but still at zero left offset.
>>
>> I put a reproducible case online:
>> http://www.tddsworld.com/bugs/autocompleter_opera9_issue/index.html
>>
>> It doesn''t use any positioned container. This very page works
fine on
>> MSIE 6, Firefox 1.5 and Konqueror 3.5.2. I haven''t got Safari
>> feedback
>> yet.
>>
>> Position.clone, which is Prototype stuff, does seem to be the culprit
>> here, but I need a solution quick. Those willing to tinker with this
>> code can find a ZIP file on the online demo''s parent
directory.
>>
>> Thanks in advance all,
>>
>> -- 
>> Christophe Porteneuve
>>
>>
>>>
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---