In safari 4 I get the "ready" alert but no anchor clicks result in a
"click" alert. However in Firefox 3 both alerts work just fine. Has
anybody else experienced this?
I've checked and re-checked this. I think the above is true. I have
had to resort to the debug JS below which works
document.observe("dom:loaded", function() {
// the element in which we will observe all clicks and capture
// ones originating from pagination links
var container = $(document.body);
if (container) {
container.observe('click', function(e) {
var el = e.element();
if (el.match('a')) {
alert("click");
}
});
}
I have been using lowpro heavily on a site and in Safari 4 there is no
problem. It also works in Firefox 3 and IE8. However, everything is
broken in Firefox 3.5 beta4. For some reason, none of the Behavior
initialize functions seem to be called and prototype fails with a
'recursion' error on event dispatch. This is only for Firefox 3.5
beta. Anyone else experience this problem?
On 19 May, 13:46, Nathan <XGamer...@gmail.com> wrote:
> I have been using lowpro heavily on a site and in Safari 4 there is no
> problem. It also works in Firefox 3 and IE8. However, everything is
> broken in Firefox 3.5 beta4. For some reason, none of the Behavior
> initialize functions seem to be called and prototype fails with a
> 'recursion' error on event dispatch. This is only for Firefox 3.5
> beta. Anyone else experience this problem?
Do you experience the prototype recursion bug on pages using only
prototype and not low pro?
No oddly enougn it seems to be a combination of the two and actually
applying / defining behaviors that causes the aforementioned issue.
There seems to be some incompatibilities between Firefox 3.5 and
lowpro. I am curious is able to can confirm this issue.
On 19 May, 05:35, MRoderick <roderick.mor...@gmail.com> wrote:
> On 19 May, 13:46, Nathan <XGamer...@gmail.com> wrote:
> > I have been using lowpro heavily on a site and in Safari 4 there is no
> > problem. It also works in Firefox 3 and IE8. However, everything is
> > broken in Firefox 3.5 beta4. For some reason, none of the Behavior
> > initialize functions seem to be called and prototype fails with a
> > 'recursion' error on event dispatch. This is only for Firefox 3.5
> > beta. Anyone else experience this problem?
> Do you experience the prototype recursion bug on pages using only
> prototype and not low pro?
On 20 May, 06:32, Nathan <XGamer...@gmail.com> wrote:
> No oddly enougn it seems to be a combination of the two and actually
> applying / defining behaviors that causes the aforementioned issue.
> There seems to be some incompatibilities between Firefox 3.5 and
> lowpro. I am curious is able to can confirm this issue.
Nathan, I've just created a sample page using Prototype 1.6.0.3 and
Low Pro 0.5. On it I've created a behaviour that simple changes the
colour of all h1 elements.
Viewing the page in Firefox 3.5b4 on OS X I get no exceptions.
Are you using a recent Low Pro version?
A few code snippets on pastie might go a long way ;-)
> On 20 May, 06:32, Nathan <XGamer...@gmail.com> wrote:
> > No oddly enougn it seems to be a combination of the two and actually
> > applying / defining behaviors that causes the aforementioned issue.
> > There seems to be some incompatibilities between Firefox 3.5 and
> > lowpro. I am curious is able to can confirm this issue.
> Nathan, I've just created a sample page using Prototype 1.6.0.3 and
> Low Pro 0.5. On it I've created a behaviour that simple changes the
> colour of all h1 elements.
> Viewing the page in Firefox 3.5b4 on OS X I get no exceptions.
> Are you using a recent Low Pro version?
> A few code snippets on pastie might go a long way ;-)
Ok I created an extremely simple example which demonstrates the issue
for me at least. In a nutshell, behavior initialize functions are not
working as expected. The sample explains it all:
On 20 May, 12:01, Nathan <XGamer...@gmail.com> wrote:
> Ok I created an extremely simple example which demonstrates the issue
> for me at least. In a nutshell, behavior initialize functions are not
> working as expected. The sample explains it all:
Hmm that worries me in that the latest nightly says 3.6a1 meaning it
might come out after 3.5 is released right? This seems like a rather
large issue which will break pretty much any lowpro sites which use
custom behaviors. I spent some time trying to fix it in lowpro itself
and had no luck as well. I guess this could be a bug in firefox 3.5
rather than in lowpro...not going to bode well for me tho once ff3.5
is released with the site entirely broken haha.
On 20 May, 20:07, Nathan <XGamer...@gmail.com> wrote:
> Hmm that worries me in that the latest nightly says 3.6a1 meaning it
> might come out after 3.5 is released right? This seems like a rather
> large issue which will break pretty much any lowpro sites which use
> custom behaviors. I spent some time trying to fix it in lowpro itself
> and had no luck as well. I guess this could be a bug in firefox 3.5
> rather than in lowpro...not going to bode well for me tho once ff3.5
> is released with the site entirely broken haha.
It worries me as well ... and not being able to get Firebug's console
working properly (or at all) in Firefox 3.5b4 is really annoying.
I've become very dependent on Firebug and am so glad I donated $10 a
few years ago ;-)
I am unsure what exactly causes the error, and don't really know
anyone working directly or indirectly on Firefox. But, this issue
clearly needs to be adressed, as I've seen several indications that
3.5 will launch soon(ish).
Even though your little error demonstration is very nice, I am not
sure that it is accurate enough to actually get attention from Firefox
developers if it was to be submitted as a bug on bugzilla. Perhaps Dan
can lend some attention, to figure out if this is in fact a Firefox
bug, or a Low Pro bug ... that would at least point us in the right
direction :-)
Yes, I agree. I would love for Dan to be able to help us make sense of
this issue. At first glance it seems almost nonsensical that the
initialize events for behaviors never applied would be randomly firing
by simply being defined but perhaps its a simple fix for the right set
of eyes. The weirdest thing is that it works in 3.6 alpha though...
Well good news! Downloaded a new firefox 3.5 nightly (Shiretoko/
3.5pre) and this version works perfectly with my sample case and with
my full website. They must have fixed the bug. This is excellent
excellent news for me and lowpro users everywhere. Crisis averted. I
can't wait for 3.5b5 which will hopefully incorporate this change.
On 31 May, 09:46, Nathan <XGamer...@gmail.com> wrote:
> Well good news! Downloaded a new firefox 3.5 nightly (Shiretoko/
> 3.5pre) and this version works perfectly with my sample case and with
> my full website. They must have fixed the bug. This is excellent
> excellent news for me and lowpro users everywhere. Crisis averted. I
> can't wait for 3.5b5 which will hopefully incorporate this change.
Yep, that's good news. I expected it to be the case as it looked more
like a regression in Firefox than a bug in Low Pro.
Thanks for letting us know, Nathan.
On Sun, May 31, 2009 at 11:48 AM, MRoderick <roderick.mor...@gmail.com> wrote:
> On 31 May, 09:46, Nathan <XGamer...@gmail.com> wrote:
>> Well good news! Downloaded a new firefox 3.5 nightly (Shiretoko/
>> 3.5pre) and this version works perfectly with my sample case and with
>> my full website. They must have fixed the bug. This is excellent
>> excellent news for me and lowpro users everywhere. Crisis averted. I
>> can't wait for 3.5b5 which will hopefully incorporate this change.
> Yep, that's good news. I expected it to be the case as it looked more
> like a regression in Firefox than a bug in Low Pro.
> Thanks for letting us know, Nathan.
> On Sun, May 31, 2009 at 11:48 AM, MRoderick <roderick.mor...@gmail.com> wrote:
> > On 31 May, 09:46, Nathan <XGamer...@gmail.com> wrote:
> >> Well good news! Downloaded a new firefox 3.5 nightly (Shiretoko/
> >> 3.5pre) and this version works perfectly with my sample case and with
> >> my full website. They must have fixed the bug. This is excellent
> >> excellent news for me and lowpro users everywhere. Crisis averted. I
> >> can't wait for 3.5b5 which will hopefully incorporate this change.
> > That is great news! Thanks for reporting it :-)
> This prob seemed to go away, but has now come back (for me) with the
> latestFirefoxRC for Mac. ANyone else seeing this?
> On 31 May, 11:51, Dan Webb <d...@danwebb.net> wrote:
> > Yep, that's good news. I expected it to be the case as it looked more
> > like a regression inFirefoxthan a bug in Low Pro.
> > Thanks for letting us know, Nathan.
> > On Sun, May 31, 2009 at 11:48 AM, MRoderick <roderick.mor...@gmail.com> wrote:
> > > On 31 May, 09:46, Nathan <XGamer...@gmail.com> wrote:
> > >> Well good news! Downloaded a newfirefox3.5 nightly (Shiretoko/
> > >> 3.5pre) and this version works perfectly with my sample case and with
> > >> my full website. They must have fixed the bug. This is excellent
> > >> excellent news for me and lowpro users everywhere. Crisis averted. I
> > >> can't wait for 3.5b5 which will hopefully incorporate this change.
> > > That is great news! Thanks for reporting it :-)
|
