Hey all, I''ve Googled and searched for this answer numerous times, but can''t find it. Apologies if this has been posted here before. I have a frameset in IE7 with a top and bottom frame (I know... frames suck. No choice here). The bottom frame is where all the action is, specifically, a portal with draggable (sortable, actually) portlets. Anyway, I get this funky problem where the content overlaps the native IE scrollbars on the left and bottom when Scriptaculous and Prototype are included in the document. I have debugged such that all elements are unstyled, so I know it''s not any styles on my side. The problem happens no matter what when Prototype and Scriptaculous are included, and when they are removed the problem goes away. That said, outside of a frameset, there is no overlap and things work fine when the two libraries exist in the page. Has anyone ever seen this? If so, has anyone found a solution? Many thanks, Robyn --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
Just to clarify, I''m using Scriptaculous 1.7.0_beta1 and Prototype 1.5.0_rc2 --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
Can you reproduce the problem with the last proven/stable release of Scriptaculous? Robyn <robynmarie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: Just to clarify, I''m using Scriptaculous 1.7.0_beta1 and Prototype 1.5.0_rc2 --------------------------------- Everyone is raving about the all-new Yahoo! Mail beta. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
Yes, I can reproduce it with the Scriptaculous 1.6.5 release, using Prototype 1.5.0_rc1. (I assume this is the latest stable release. I couldn''t find any below that one.) Robyn --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
In order to fix a similar problem I had to explicitly set the CSS
position attributes for the element that was having the problem as well
as all its ancestors (except for the body element).
So if I had
<body>
<div>
<p>
and <p> was the problem element I''d have
p { position: relative; }
div { position: relative; }
in my stylesheet.
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
Brian, Thanks. I will give that a try. Robyn On 12/7/06, Brian Gibson <brian.gibson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > In order to fix a similar problem I had to explicitly set the CSS > position attributes for the element that was having the problem as well > as all its ancestors (except for the body element). > > So if I had > > <body> > <div> > <p> > > and <p> was the problem element I''d have > > p { position: relative; } > > div { position: relative; } > > in my stylesheet. > > > > >--~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---