TableDnD
TableDnD copied to clipboard
isocra
Plugin failing silently on Firefox 22 and Chrome in Windows 7
Hi there, with reference to this:
https://github.com/isocra/TableDnD/issues/30
One of our customers is having this issue and I've witnessed it on their computer via remote support. Dragging the draggable item just results in the image trying to be dragged around (as in the default behaviour when one drags something that isn't draggable in these browsers). It works fine in Internet Explorer though.
I have a test machine running Windows 7 Enterprise and it works fine in Firefox 22 and Chrome.
The biggest problem is that, looking at the console, there are no error messages at all. I tried in Firefox's default console and also with Firebug.
The customer reports that it also doesn't work on her work machine. The home machine is running Windows 7 Home Premium with SP1.
Any troubleshooting tips would be greatly appreciated. I've already tried disabling addons and reinstalling the browser (Firefox).
You seem to be on the right track, patience and persistence is the best weapons at your disposal when hunting down edge cases like these.
I suggest that you try running the examples index.html because these start of with the very basic tableDnD and then progressively adds more features. The goal is to first see if you can manage to get the most basic functionality working, at least there is hope then =) Then try and add as litte additional functionality back and testing thoroughly after every addition in the hopes of isolating the cause.
Once you found the cause of the problem you should work your way back again. One by one removing the functionality that didn't pose a problem. Keep testing to ensure that the problem remains after removing the "working" features. The reasoning for this is twofold:
Isolation to ensure that the cul/prit is cause alone on its own and not due to a combination of a few settings.
When you are sure you have found the simplest combination that still causes the faults you can create that as an example of the problem, a simple table with the minimum markup, no styles and no other libraries only what is needed to reproduce the fault. Submitting this example will enable others to try it as well, only if they can also see the fault (as you have realised yourself) can they try and help you fix it.
Hang in there and shout if you need a hand.
Thanks Nick. Funny you should reply just now as I only just took another look at this about an hour ago! I'll get in touch with the client and see if I can commandeer her computer to run these tests :)
Cheers, Brendon
On Mon, Aug 26, 2013 at 11:45 AM, Nick Lombard [email protected]:
You seem to be on the right track, patience and persistence is the best weapons at your disposal when hunting down edge cases like these.
I suggest that you try running the examples index.html because these start of with the very basic tableDnD and then progressively adds more features. The goal is to first see if you can manage to get the most basic functionality working, at least there is hope then =) Then try and add as litte additional functionality back and testing thoroughly after every addition in the hopes of isolating the cause.
Once you found the cause of the problem you should work your way back again. One by one removing the functionality that didn't pose a problem. Keep testing to ensure that the problem remains after removing the "working" features. The reasoning for this is twofold:
Isolation to ensure that the cul/prit is cause alone on its own and not due to a combination of a few settings.
When you are sure you have found the simplest combination that still causes the faults you can create that as an example of the problem, a simple table with the minimum markup, no styles and no other libraries only what is needed to reproduce the fault. Submitting this example will enable others to try it as well, only if they can also see the fault (as you have realised yourself) can they try and help you fix it.
Hang in there and shout if you need a hand.
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-23238017 .
@brendon How did it go? I've been holding thumbs for you! They'le turning blue already =)
Hehe! Hi Nick, I'm sorry to say I didn't hear back from the client, and since then I've had my tonsils out so I've been out of action. Once I'm back on deck I'll try to get in touch with her again and go from there :)
I've never heard of holding thumbs before! :) I'm guessing it's like crossing fingers? :D
On Thu, Sep 19, 2013 at 8:20 AM, Nick Lombard [email protected]:
@brendon https://github.com/brendon How did it go? I've been holding thumbs for you! They'le turning blue already =)
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-24695998 .
@brendon crossing fingers also means you're lying hoping not to get caught, or perhaps that's another South African thing. Holding thumbs is closer to thumbs up if I have to guess but you're still in the same ball park. =)
I am closing this issue but feel free to keep using it.
Hope your throat feels better already!
Hehe, thanks for that. Yea in NZ fingers crossed means hoping for the best. I think the Americans use it to get out of verbal contracts :) Thumbs up is more like 'choice' or 'sweet as' or 'all good' here :)
I've learned something new! :D
I'll keep you posted.
On Mon, Sep 23, 2013 at 12:40 PM, Nick Lombard [email protected]:
@brendon https://github.com/brendon crossing fingers also means you're lying hoping not to get caught, or perhaps that's another South African thing. Holding thumbs is closer to thumbs up if I have to guess but you're still in the same ball park. =)
I am closing this issue but feel free to keep using it.
Hope your throat feels better already!
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-24894399 .
Since holding thumbs didn't do any good at Eden Park I'll try crossing fingers when the all blacks visit us weekend after next. =)
Lol, just had a call with the customer and went to test it on another computer of hers within her school network and it worked fine. Turns out it's only not working on her home pc so I've booked a time with her next week to take a look at that. I'm certain it's a plugin or other glitch causing the problem, but will be interesting to get to the bottom of it :) I'll keep you posted :)
On Mon, Sep 23, 2013 at 2:06 PM, Nick Lombard [email protected]:
At least you don't have us to worry about there :p
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-24895911 .
Wheeeee \o/ well done!
So @brendon are you saying it's not working? Is it running the latest version? We've got touch support built in the debate around #26 is whether this is something we should be doing ourselves or instead rely on a trusted wheel manufacturer instead.
It works on Android and @isocra reported it working on iOS too so what is it doing to you there? Did we not remove the warning... memory is going hazy too...
Hehe, Because I was too lazy to chuck the project on my server and it doesn't work by default when run locally (due to the protocol relative references to jquery etc... file:// fail) I just went to your blog page and tried to ignore that it was written in 2008. If that's not the latest version then I will stop being lazy and get her to check a hosted version of the latest script :)
Her computer is an Acer desktop I believe, with a touch screen. I was using the latest version of Chrome on Windows 7. I remember when I tested last Firefox also failed, but perhaps they fixed something in their latest release.
I checked our system too (which is using your latest 0.9rc1) and it failed too, so perhaps this isn't solved for all touch interfaces? Slightly tricky/annoying to test given the hardware required! Any thoughts?
https://github.com/isocra/TableDnD/blob/master/js/jquery.tablednd.0.9.rc1.js
be latest revision @brendon
Thanks Nick. I'll give it a whirl :)
On Tue, Oct 22, 2013 at 4:03 AM, Nick Lombard [email protected]:
https://github.com/isocra/TableDnD/blob/master/js/jquery.tablednd.0.9.rc1.js
be latest revision @brendon https://github.com/brendon
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-26724830 .
Sorry, I misunderstood you. I'm already running that version and it's still having the problem. :)
On Tue, Oct 22, 2013 at 10:44 AM, Brendon Muir [email protected] wrote:
Thanks Nick. I'll give it a whirl :)
On Tue, Oct 22, 2013 at 4:03 AM, Nick Lombard [email protected]:
https://github.com/isocra/TableDnD/blob/master/js/jquery.tablednd.0.9.rc1.js
be latest revision @brendon https://github.com/brendon
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-26724830 .
Ahh I see so this is on a desktop with touch screen, hmmmm tricky indeed.
Reopening issue
Indeed, it was a bit out of left field.
On Sat, Nov 16, 2013 at 4:37 AM, Nick Lombard [email protected]:
Ahh I see so this is on a desktop with touch screen, hmmmm tricky indeed.
Reopening issue
— Reply to this email directly or view it on GitHubhttps://github.com/isocra/TableDnD/issues/31#issuecomment-28577633 .
This can be closed too I think due to: https://github.com/isocra/TableDnD/pull/44