[Moo] Re: Noobslide number 6 does not work
The only thing I did to fix the bug on Chrome was , as Sandy suggested, add delete Function.prototype.bind; BEFORE all the other javascript files/code. I didn't make any changes to the noobslide code itself. Feel free to copy my example code as a starting point ;) Chris On 8 ene, 20:41, guswah wrote: > I notice, Chris, that your sample page is still posted, and thanks for that. > I've been using it and probably others are too. > > So is there a specific workaround for the script that allows it to function > normally under Chrome? I notice that your Noobslide sample works fine on > Chrome, but my own test page does not. Which suggests that you've made > changes to your javascript that I'd like to incorporate to ensure that I'm > good to go on Chrome as well as FF/IE et al. > > Your help, both Chris and Sandy, is much appreciated. > -- > View this message in > context:http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p42744... > Sent from the MooTools Users mailing list archive at Nabble.com.
Re: [Moo] Re: Noobslide number 6 does not work
I notice, Chris, that your sample page is still posted, and thanks for that. I've been using it and probably others are too. So is there a specific workaround for the script that allows it to function normally under Chrome? I notice that your Noobslide sample works fine on Chrome, but my own test page does not. Which suggests that you've made changes to your javascript that I'd like to incorporate to ensure that I'm good to go on Chrome as well as FF/IE et al. Your help, both Chris and Sandy, is much appreciated. -- View this message in context: http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p4274471.html Sent from the MooTools Users mailing list archive at Nabble.com.
[Moo] Re: Noobslide number 6 does not work
> > I tried adding your suggested line of javascript to remove > > "Function.prototype.bind;" but that made no difference. > > That is a surprise. Calling "delete Function.prototype.bind" before > loading Core is a fix for my affected boxes. What does > console.log(Function.prototype.bind.toString()) show before/after the > delete? Appologies, sorry it was working I had made a silly copy & paste error that was breaking it :( Have a good sleep (I just got up ;) ) Chris On Jan 5, 9:50 am, Sanford Whiteman wrote: > Thank you!!! I really appreciate you continuing to explore this. > > > I tried adding your suggested line of javascript to remove > > "Function.prototype.bind;" but that made no difference. > > That is a surprise. Calling "delete Function.prototype.bind" before > loading Core is a fix for my affected boxes. What does > console.log(Function.prototype.bind.toString()) show before/after the > delete? > > (Off to sleep for a while now.) > > -- S.
Re: [Moo] Re: Noobslide number 6 does not work
Thank you!!! I really appreciate you continuing to explore this. > I tried adding your suggested line of javascript to remove > "Function.prototype.bind;" but that made no difference. That is a surprise. Calling "delete Function.prototype.bind" before loading Core is a fix for my affected boxes. What does console.log(Function.prototype.bind.toString()) show before/after the delete? (Off to sleep for a while now.) -- S.
[Moo] Re: Noobslide number 6 does not work
OK, as requested I have installed a Chrome theme and, as you suspected, the gallery stops working :( I tried adding your suggested line of javascript to remove "Function.prototype.bind;" but that made no difference. Finally, I then deactivated the theme and even restarted Chrome (next thing to try is a reboot) however the script is now not working either (ie with the default theme). It appears, again as you said, that once a theme (extension) has been activated once, the offending function is initiated every time. So, at least you have discovered why it works for some and not others (ie the use of a theme or possibly any other extension) - well done! :) Chris On 5 ene, 09:10, Sanford Whiteman wrote: > > so the prototype is being modified by Chrome itself > > Could someone with Chrome 3.x (latest stable) please go get a Chrome > theme, for example their featured "Stargazer" theme? Pretty please? > > Then go to Chris' NoobSlide test page at > > http://www.cbolson.com/sandbox/mootools/noobslide/demo-6.html > > You may finally see the Function.prototype.bind collision that I've > been a crazy-man about. Symptom: mousing over a thumbnail doesn't > cause the corresponding image to slide into the main area. (Also JS > errors easily visible in console.) Cause: Moo bind is preempted. > > If it doesn't happen right away, try installing another theme, closing > out Chrome, and going back in. Or switch back to the Default theme and > then restart. Some combination is almost sure to trigger the alternate > bind to load. I've now gotten it to break on 4 different boxes, 2K3 > and XP, by installing themes. > > Found note at > > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/resou... > > which suggests that their internal JS may only be loaded as part of > the extension loading process (themes are considered extensions). If > you had a theme installed at any point (even if you are now using the > Default theme), the extensions/ folder remains on disk. > Some of the time when theme folder/s are detected -- but seemingly not > in every permutation -- Chrome will preload "privileged chrome > extension related javascript APIs" including their incompatible > version of bind. > > Anybody give me some feedback on this over the next week? TIA. > > -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> so the prototype is being modified by Chrome itself Could someone with Chrome 3.x (latest stable) please go get a Chrome theme, for example their featured "Stargazer" theme? Pretty please? Then go to Chris' NoobSlide test page at http://www.cbolson.com/sandbox/mootools/noobslide/demo-6.html You may finally see the Function.prototype.bind collision that I've been a crazy-man about. Symptom: mousing over a thumbnail doesn't cause the corresponding image to slide into the main area. (Also JS errors easily visible in console.) Cause: Moo bind is preempted. If it doesn't happen right away, try installing another theme, closing out Chrome, and going back in. Or switch back to the Default theme and then restart. Some combination is almost sure to trigger the alternate bind to load. I've now gotten it to break on 4 different boxes, 2K3 and XP, by installing themes. Found note at http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/resources/extension_process_bindings.js?view=markup&pathrev=24175 which suggests that their internal JS may only be loaded as part of the extension loading process (themes are considered extensions). If you had a theme installed at any point (even if you are now using the Default theme), the extensions/ folder remains on disk. Some of the time when theme folder/s are detected -- but seemingly not in every permutation -- Chrome will preload "privileged chrome extension related javascript APIs" including their incompatible version of bind. Anybody give me some feedback on this over the next week? TIA. -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> A couple of installs of Chrome 3 on 2K3 Server appear to not show the > bug. Only on XP so far. I am trying to compare the binaries and see > what, if any, strangeness I can find. This could have me on the ledge shortly. I think I have to stop and just recommend the workaround -- before loading MooTools delete Function.prototype.bind; This clears it up, establishing that the buggy area is just where I thought (there are no other frameworks on the page -- it's the NoobSlide demo page -- and no plug-ins, so the prototype is being modified by Chrome itself). -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> I should point out that I am using Chrome on XP via Parallels (ie on a > Mac) Okay, I am talking about real XP, but that in the case of Chrome should make no difference. A couple of installs of Chrome 3 on 2K3 Server appear to not show the bug. Only on XP so far. I am trying to compare the binaries and see what, if any, strangeness I can find. -- Sandy
[Moo] Re: Noobslide number 6 does not work
I should point out that I am using Chrome on XP via Parallels (ie on a Mac) I have also just installed Chrome version 4.0.249.30 on the Mac to test it there and again it works correctly with no bugs. Finally, just to prove (to myself) that it wasn't just my computer being "nice" to me, I booted up a remote server via browsercam.com to test it and again, I am afraid to say, I got no errors. Chris On 5 ene, 01:08, Sanford Whiteman wrote: > > I have just tested my test on on Chrome version 3.0.195.38 (latest > > version) and it all appears to work correctly. > > No error messages and mouseover/enter looks to be working as expected. > > Just installed fresh Chrome 3.0.195.38 (same version I had tested on > originally, BTW) on another machine and it shows the same bug I > described + Guswah is noting as well. > > There's something wacky here... still looking. > > -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> I have just tested my test on on Chrome version 3.0.195.38 (latest > version) and it all appears to work correctly. > No error messages and mouseover/enter looks to be working as expected. Just installed fresh Chrome 3.0.195.38 (same version I had tested on originally, BTW) on another machine and it shows the same bug I described + Guswah is noting as well. There's something wacky here... still looking. -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
cbolson wrote: > > I have just tested my test on on Chrome version 3.0.195.38 (latest > version) and it all appears to work correctly. > No error messages and mouseover/enter looks to be working as expected. Well, that's too bad. I'm on the same version, but it continues to freeze upon hover. cbolson wrote: > > I have just added a few more images (copies of the others to be honest > so as to not upload more images) with no problems. Yes, it looks splendid, and I presume some added css will arrange it all quite nicely. I don't recall which forum I visited yesterday that mentioned problems in adding photos. I will do as you've suggested with the greatest of thanks. As for Chrome ... ? Maybe if I move onto another computer the result will differ. -- View this message in context: http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p4252745.html Sent from the MooTools Users mailing list archive at Nabble.com.
[Moo] Re: Noobslide number 6 does not work
Sorry, not had a chance to get back on this one until now. I have just tested my test on on Chrome version 3.0.195.38 (latest version) and it all appears to work correctly. No error messages and mouseover/enter looks to be working as expected. > On another tack, I noticed there were Noobslide users who struggled with the > addition of slides beyond the eight in the demo. Has anyone found a way to > increase that without a lot of work? I have just added a few more images (copies of the others to be honest so as to not upload more images) with no problems http://www.cbolson.com/sandbox/mootools/noobslide/demo-6.html All I did was add more thumbs, images and items to the array. What sort of problems are the other Noobslide users you mention experiencing? Chris On 4 ene, 23:52, guswah wrote: > On Chrome my test page loads visually intact but the script breaks as soon as > it's put to work, meaning any button activity or even a hover. So no, the > script is not currently functional on primary browsers. > > -- > View this message in > context:http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p42525... > Sent from the MooTools Users mailing list archive at Nabble.com.
Re: [Moo] Re: Noobslide number 6 does not work
On Chrome my test page loads visually intact but the script breaks as soon as it's put to work, meaning any button activity or even a hover. So no, the script is not currently functional on primary browsers. -- View this message in context: http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p4252503.html Sent from the MooTools Users mailing list archive at Nabble.com.
Re: [Moo] Re: Noobslide number 6 does not work
> I haven't tried it on Chrome, but FF and IE both appear to deliver > the desired result. Please do test on Chrome 3 for add'l verification. > On another tack, I noticed there were Noobslide users who struggled > with the addition of slides beyond the eight in the demo. Has anyone > found a way to increase that without a lot of work? (Bearing in mind > that I'm apparently nowhere near the level of expertise of you > folks.) I'll look at it later, since I have this stuff in MooShell already. -- S.
Re: [Moo] Re: Noobslide number 6 does not work
> While Chris and I are figuring where an actual bug is at, can you tell us > what you actually tried? Surely you didn't get caught up just by > sampleObjectItems being defined under Sample 5... the JS console > should have cleared that up pretty quick. Actually I did get caught up in the sampleObjectItems because when I tried to redefine it I likely made a typo and was too tired to sleuth out the problem. Consequently I only got sample 6 to work when I left the bones of sample 5 on my html page. I've since overwritten my version with yours. I haven't tried it on Chrome, but FF and IE both appear to deliver the desired result. On another tack, I noticed there were Noobslide users who struggled with the addition of slides beyond the eight in the demo. Has anyone found a way to increase that without a lot of work? (Bearing in mind that I'm apparently nowhere near the level of expertise of you folks.) -- View this message in context: http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p4252336.html Sent from the MooTools Users mailing list archive at Nabble.com.
Re: [Moo] Re: Noobslide number 6 does not work
> I have Chrome 4 and it's not throwing any errors - so if there was an > issue with 3, it's gone in 4 - (what OS are you using? I'm on XP, I'll > check the OSX later) It's XP, Chrome 3 very latest stable. I tried the Chrome 4 Beta elsewhere and you're right, no bug there. Based on glancing at their trunk, I think they've now namespaced it as goog.bind only, instead of also touching Function.prototype.bind. It is interesting that these functions exist -- though their source language is JS, I'm assuming they are compiled or somehow optimized when Chrome starts? Wonder if detecting + using these could be faster than using the Moo varieties? Yes, you would be embracing non-standard stuff, even if such helper functions have become "framework-standard"; and already we see a Moo-familiar function name but a Moo-unfamiliar signature. I dunno. -- Sandy
[Moo] Re: Noobslide number 6 does not work
I have Chrome 4 and it's not throwing any errors - so if there was an issue with 3, it's gone in 4 - (what OS are you using? I'm on XP, I'll check the OSX later) On Jan 3, 11:30 pm, Sanford Whiteman wrote: > > Chrome 3 - fail > > OK, this is why there is no one "reference" browser. :P > > Chrome has its own native Function.prototype.bind (see > Chrome/Application//resources/inspector/base.js:897). And its > own bind does not accept an array of arguments. This explains why > bindWithEvent would always work, while bind was showing errors. I > found the applicable code in NoobSlide to work around, but it's > actually a bug in the whole environment (Moo on Chrome) -- I think. > > Will someone please make sure I am not going crazy? > > -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> Chrome 3 - fail OK, this is why there is no one "reference" browser. :P Chromehasitsownnative Function.prototype.bind (see Chrome/Application//resources/inspector/base.js:897). And its own bind does not accept an array of arguments. This explains why bindWithEvent would always work, while bind was showing errors. I found the applicable code in NoobSlide to work around, but it's actually a bug in the whole environment (Moo on Chrome) -- I think. Will someone please make sure I am not going crazy? -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> show me anyone who has successfully separated sample 6 from sample 5 > without rewriting the script, and I'll be really impressed. While Chris and I are figuring where an actual bug is at, can you tell us what you actually tried? Surely you didn't get caught up just by sampleObjectItems being defined under Sample 5... the JS console should have cleared that up pretty quick. -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> I have tested it on Firefox, Safari, Opera and IE and they all work in > exactly the same manner. Chrome 3 - fail I originally thought just as you did that the missing piece was just that sampleObjectItems array -- but I happened to test it in Chrome first and found the event bug there. Maybe it works in more browsers than IE, but it is not built right overall. -- Sandy
[Moo] Re: Noobslide number 6 does not work
> Not so. The example you have up is only fully functional in IE. I'm not sure what you are referring too :( I have tested it on Firefox, Safari, Opera and IE and they all work in exactly the same manner. As far as I can tell the mouseenter event (I presume that you are referring to the event on the thumnails) works correctly in all the browsers I tested. Am I missing something? Chris On 3 ene, 21:37, Sanford Whiteman wrote: > > The only thing that was required to do to get demo 6 working is to > > make sure that the array of "sampleObjectItem" is present as this is > > used to define the slide items. > > Not so. The example you have up is only fully functional in IE. > > The bug is in _class.noobSlide.js:113, ::handleButtons: > > handles[i].addEvent(this.handle_event,this.walk.bind(this,[i,true])); > > This runs a bound ::walk on mouseEnter, attempting to apply an array > of arguments to it [item = i, manual = true]. But this should be > bindWithEvent (and ::walk needs to expect an event in kind). > > As a result of the bug, the slides never change on mouseEnter, since i > = null. Because of the passed-event-vs-window.event difference in IE, > it still works there. > > -- Sandy
Re: [Moo] Re: Noobslide number 6 does not work
> The only thing that was required to do to get demo 6 working is to > make sure that the array of "sampleObjectItem" is present as this is > used to define the slide items. Not so. The example you have up is only fully functional in IE. The bug is in _class.noobSlide.js:113, ::handleButtons: handles[i].addEvent(this.handle_event,this.walk.bind(this,[i,true])); This runs a bound ::walk on mouseEnter, attempting to apply an array of arguments to it [item = i, manual = true]. But this should be bindWithEvent (and ::walk needs to expect an event in kind). As a result of the bug, the slides never change on mouseEnter, since i = null. Because of the passed-event-vs-window.event difference in IE, it still works there. -- Sandy
[Moo] Re: Noobslide number 6 does not work
Hi, Whilst I agree with you that the noobSlide class is poorly documented, I disagree in that it is complicated to get working. Taking the source code from the original script it took me about 2 minutes to get a standalone working version of examples 5 and 6. http://www.cbolson.com/sandbox/mootools/noobslide/demo-5.html http://www.cbolson.com/sandbox/mootools/noobslide/demo-6.html The only thing that was required to do to get demo 6 working is to make sure that the array of "sampleObjectItem" is present as this is used to define the slide items. Chris On 3 ene, 18:53, guswah wrote: > I've installed nearly a hundred Mootools, JQuery, etc. frameworks and > plugins. Never have I seen one so inherently unsuitable for webmasters to > disseminate. Is 'Elvis Parsley' chuckling? I think this is the point where > most folks just give up and use another script. Unless you're a js guru, > don't waste your time on sample 6, folks. You can emulate the exact > structure and syntax above, but there is no way in creation it works, or at > least it doesn't for me. > > To be fair, I have no doubt about the author's talent, but it does appear > that his first language is not English. The examples on his presentation > are completely undocumented and without corroborating support. There are a > lot of sites that post the noobslide link, which is good for SEO, but show > me anyone who has successfully separated sample 6 from sample 5 without > rewriting the script, and I'll be really impressed. > -- > View this message in > context:http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p42466... > Sent from the MooTools Users mailing list archive at Nabble.com.
[Moo] Re: Noobslide number 6 does not work
I've installed nearly a hundred Mootools, JQuery, etc. frameworks and plugins. Never have I seen one so inherently unsuitable for webmasters to disseminate. Is 'Elvis Parsley' chuckling? I think this is the point where most folks just give up and use another script. Unless you're a js guru, don't waste your time on sample 6, folks. You can emulate the exact structure and syntax above, but there is no way in creation it works, or at least it doesn't for me. To be fair, I have no doubt about the author's talent, but it does appear that his first language is not English. The examples on his presentation are completely undocumented and without corroborating support. There are a lot of sites that post the noobslide link, which is good for SEO, but show me anyone who has successfully separated sample 6 from sample 5 without rewriting the script, and I'll be really impressed. -- View this message in context: http://n2.nabble.com/Noobslide-number-6-does-not-work-tp1129480p4246645.html Sent from the MooTools Users mailing list archive at Nabble.com.
