Rails spinoffs - Feb 2008 - Prototype.js 1.6.0-base script issues on Safari 3 (Mac & Win) Bounty

I''ve been asking questions related to this on IRC for the past month
or so, on and off, but have gotten no answers. I''ve since gotten
approval for a $150 bounty for the first person that can solve this
issue and offered it up today (also on IRC) without any takers, but
the more eyes the better.

I wrote three scripts (tabbedView.js, flyoutMenu.js, and
centerImages.js) using Prototype.js 1.6.0 and they work in our target
browsers (Firefox 2, Safari 2, Safari 3, IE 6 & 7, Opera 9) when
running a local snapshot of a page & the scripts. But here''s the
problem, in Safari 3 (Mac & Windows), the element manipulation that
the scripts do doesn''t appear to get applied when run from our live
servers, but they work fine in the rest of the target browsers.

I put in some console.log() lines to make sure that the scripts were
loading in order and in their entirety as well as when their functions
observing ''dom:loaded'' are loaded. This all goes off without a
hitch,
even in Safari 3 from the live servers, yet no manipulation of the
page.

If you want to help, please take a peek at http://dev.smalldog.com/
and test in Firefox 2 & Safari 3 to see how the code should work and
what it looks like when it doesn''t (specifically the fly-out menus
from categories in the sidebar & tabs like on search results or top
dog club page).

If you''re the first to provide a solution, we''ll send you $150
via
PayPal for your trouble. Yes, even if I''ve made an extremely stupid
mistake. Let me know if you have any questions, suggestions, or
solutions.

BTW - If you have any suggestions as to how to optimize the fly-out
menus for better performance, that''d be greatly appreciated as well,
but there''s not a specific bounty for that.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

its something in one of yer other Javascripts

http://www.bruuuuuce.com/sd/index.html



On Wed, Feb 13, 2008 at 5:41 PM, morgant
<morgan.aldridge-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I''ve been asking questions related to this on IRC for the past
month
> or so, on and off, but have gotten no answers. I''ve since gotten
> approval for a $150 bounty for the first person that can solve this
> issue and offered it up today (also on IRC) without any takers, but
> the more eyes the better.
>
> I wrote three scripts (tabbedView.js, flyoutMenu.js, and
> centerImages.js) using Prototype.js 1.6.0 and they work in our target
> browsers (Firefox 2, Safari 2, Safari 3, IE 6 & 7, Opera 9) when
> running a local snapshot of a page & the scripts. But here''s
the
> problem, in Safari 3 (Mac & Windows), the element manipulation that
> the scripts do doesn''t appear to get applied when run from our
live
> servers, but they work fine in the rest of the target browsers.
>
> I put in some console.log() lines to make sure that the scripts were
> loading in order and in their entirety as well as when their functions
> observing ''dom:loaded'' are loaded. This all goes off
without a hitch,
> even in Safari 3 from the live servers, yet no manipulation of the
> page.
>
> If you want to help, please take a peek at http://dev.smalldog.com/
> and test in Firefox 2 & Safari 3 to see how the code should work and
> what it looks like when it doesn''t (specifically the fly-out menus
> from categories in the sidebar & tabs like on search results or top
> dog club page).
>
> If you''re the first to provide a solution, we''ll send you
$150 via
> PayPal for your trouble. Yes, even if I''ve made an extremely
stupid
> mistake. Let me know if you have any questions, suggestions, or
> solutions.
>
> BTW - If you have any suggestions as to how to optimize the fly-out
> menus for better performance, that''d be greatly appreciated as
well,
> but there''s not a specific bounty for that.
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

sorry, let me go further with that.

i copied the code from your index page.  and created index.html same for
prototype and the flyoutmenu.js

I did not copy any of the other js files, nor are they being loaded, thus i
must presume that the problem is in one of the other javascript files



On Wed, Feb 13, 2008 at 6:18 PM, Brian Williams
<brianw1975-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> its something in one of yer other Javascripts
>
> http://www.bruuuuuce.com/sd/index.html
>
>
>
>
> On Wed, Feb 13, 2008 at 5:41 PM, morgant
<morgan.aldridge-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>
> >
> > I''ve been asking questions related to this on IRC for the
past month
> > or so, on and off, but have gotten no answers. I''ve since
gotten
> > approval for a $150 bounty for the first person that can solve this
> > issue and offered it up today (also on IRC) without any takers, but
> > the more eyes the better.
> >
> > I wrote three scripts (tabbedView.js, flyoutMenu.js, and
> > centerImages.js) using Prototype.js 1.6.0 and they work in our target
> > browsers (Firefox 2, Safari 2, Safari 3, IE 6 & 7, Opera 9) when
> > running a local snapshot of a page & the scripts. But
here''s the
> > problem, in Safari 3 (Mac & Windows), the element manipulation
that
> > the scripts do doesn''t appear to get applied when run from
our live
> > servers, but they work fine in the rest of the target browsers.
> >
> > I put in some console.log() lines to make sure that the scripts were
> > loading in order and in their entirety as well as when their functions
> > observing ''dom:loaded'' are loaded. This all goes off
without a hitch,
> > even in Safari 3 from the live servers, yet no manipulation of the
> > page.
> >
> > If you want to help, please take a peek at http://dev.smalldog.com/
> > and test in Firefox 2 & Safari 3 to see how the code should work
and
> > what it looks like when it doesn''t (specifically the fly-out
menus
> > from categories in the sidebar & tabs like on search results or
top
> > dog club page).
> >
> > If you''re the first to provide a solution, we''ll
send you $150 via
> > PayPal for your trouble. Yes, even if I''ve made an extremely
stupid
> > mistake. Let me know if you have any questions, suggestions, or
> > solutions.
> >
> > BTW - If you have any suggestions as to how to optimize the fly-out
> > menus for better performance, that''d be greatly appreciated
as well,
> > but there''s not a specific bounty for that.
> > > >
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Safari has problems serving content as "application/xhtml+xml;"
I''m
not sure but maybe using "text/html" could fix the issue.

Best,
kangax
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Oh, and here''s a ticket regarding this issue for those who''s
interested. http://dev.rubyonrails.org/ticket/9798
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

On 14.2.2008, at 1.35, kangax wrote:
>
> Oh, and here''s a ticket regarding this issue for those
who''s
> interested. http://dev.rubyonrails.org/ticket/9798
That ticket is claimed to be fixed in Webkit
(http://bugs.webkit.org/show_bug.cgi?id=15467
), however, the page Morgan linked to still doesn''t worked with the  
latest nightly build (http://nightly.webkit.org/).

//jarkko

--
Jarkko Laine
http://jlaine.net
http://dotherightthing.com
http://www.railsecommerce.com
http://odesign.fi

kangax gets the bounty for his identifying the problem and providing a
feasible solution.

On Feb 14, 1:47 am, Jarkko Laine
<jar...-k1O+Gnc6WpmsTnJN9+BGXg@public.gmane.org>
wrote:
>
> On 14.2.2008, at 1.35, kangax wrote:
>
> > Oh, and here''s a ticket regarding this issue for those
who''s
> > interested.http://dev.rubyonrails.org/ticket/9798
>
> That ticket is claimed to be fixed in Webkit
(http://bugs.webkit.org/show_bug.cgi?id=15467
> ), however, the page Morgan linked to still doesn''t worked with
the
> latest nightly build (http://nightly.webkit.org/).
Yes, I''ve been doing additional testing this morning and although the
WebKit issue is, in fact, fixed in the latest nightly builds (proved
by the included test case), that hasn''t solved the issue with
prototype.js. I''ve updated the notes for the prototype.js ticket and
will look into finding a patch so that we can eventually switch our
content type back.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

On Feb 14, 2:28 pm, morgant
<morgan.aldri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Yes, I''ve been doing additional testing this morning and although
the
> WebKit issue is, in fact, fixed in the latest nightly builds (proved
> by the included test case), that hasn''t solved the issue with
> prototype.js. I''ve updated the notes for the prototype.js ticket
and
> will look into finding a patch so that we can eventually switch our
> content type back.
If possible, could you put the test case attached to that trac ticket
[1] onto a public server and serve it with the application/xhtml+xml
mime-type? I''d like to start working on this ticket, but at the moment
am not equipped to reconfigure any server I control to serve this page
up properly.

Cheers,
Andrew

[1] http://dev.rubyonrails.org/attachment/ticket/9798/test.xhtml
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---