List Info

Thread: Help: Safari/Konqueror issue with absolute div initially hidden




Help: Safari/Konqueror issue with absolute div initially hidden
user name
2006-09-09 15:48:08
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:

h
ttp://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
rubyonrails-spinoffsgooglegroups.com
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Help: Safari/Konqueror issue with absolute div initially hidden
user name
2006-09-09 16:18:04
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 <tddtddsworld.com> 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:
>
> h
ttp://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
rubyonrails-spinoffsgooglegroups.com
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Help: Safari/Konqueror issue with absolute div initially hidden
user name
2006-09-09 16:28:19
Hello Peter,

Peter Michaux a écrit :
> 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

Thanks, man.  I don't have time to investigate new
Draggable just now,
but I will, and submit sth with patch+test to the Trac.

However, I decided to apply the patch directly to the inline
style
attribute.  My <div id="photo"> now has:

  style="display: none; position: absolute"

I tested on Konq, and it works fine now.  Would you be so
kind as to
confirm this fixes it on Safari as well?

Thanks again!

-- 
Christophe Porteneuve a.k.a. TDD
"[They] did not know it was impossible, so they did
it." --Mark Twain
Email: tddtddsworld.com

--~--~---------~--~----~------------~-------~--~----~
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-spinoffsgooglegroups.com
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Help: Safari/Konqueror issue with absolute div initially hidden
user name
2006-09-09 16:44:56
On 9/9/06, Christophe Porteneuve <tddtddsworld.com> wrote:
>
> > 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
>
> Thanks, man.  I don't have time to investigate new
Draggable just now,
> but I will, and submit sth with patch+test to the Trac.

I figured that is what Urgent probably meant.


> However, I decided to apply the patch directly to the
inline style
> attribute.  My <div id="photo"> now
has:
>
>   style="display: none; position: absolute"
>
> I tested on Konq, and it works fine now.  Would you be
so kind as to
> confirm this fixes it on Safari as well?

It works in Safari 2.0 on OS X 10.4 but not on Safari 1.3 on
OS X
10.3.  However that isn't related to this problem.
Something else is
wrong and "Undefined value" appears.

Peter

--~--~---------~--~----~------------~-------~--~----~
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-spinoffsgooglegroups.com
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )