Hi,
I played with your zipped example a little. It is the new Draggable
line in client.js that seems to be messing up the positioning. I don't
know what is going on with the positioning in Safari when new
Draggable runs but if you want a quick hack fix adding one line seems
to work
function initPage() {
Event.observe('displayer1', 'click', handleThumbClick);
Event.observe('displayer2', 'click', handleThumbClick);
Event.observe('photo-closer', 'click', closePhoto);
new Draggable('photo', {});
$(photo).style.position='absolute';
} // initPage
That might get you started tracking down the problem in dragdrop.js
Peter
On 9/9/06, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I have this project due tomorrow night (yes, it's a Sunday...), and
> only one trick bug left, which only occurs on Safari 2 and Konqueror
> (3.5.2). I guess the Webcore/KHTML common tree goes here...
>
> You'll find a test page online:
>
> http://tddsworld.com/bugs/hidden_absolute_issue/
>
> If you want to tinker on your box, get the ZIP:
>
> http://tddsworld.com/bugs/hidden_absolute_issue.zip
>
> Try first on IE, FF or Opera: clicking a link opens a draggable DIV
> with contents inside, the whole thing being adjusted to the internal
> photo's size. The outer DIV for this (ID 'photo') is hidden in-source
> (so as to let Prototype work with hide/show), and absolute in-CSS.
>
> Konqueror and Safari don't absolutize it, and therefore leave it as a
> page-bottom, page-width-sized container.
>
> Any ideas?
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
