yeti-adaptors icon indicating copy to clipboard operation
yeti-adaptors copied to clipboard

quit yeti adaptor throws error in IE8 (XP)

Open jayarjo opened this issue 12 years ago • 9 comments

bunyip was hanging in my console, so I went to actual browser to see what might be the reason for it and saw IE8 on XP throwing this:

'$yetify.socket.json' is null or not an object qunit-yeti-adaptor.js, line 21 character 9

bunyip should probably survive it anyway and hint something back into the console.

jayarjo avatar Jun 10 '12 08:06 jayarjo

Hmm I am getting feedback from IE8 VMs on browserstack in bunyip saying a script error has occured.

As for why it's failing I'll need to investigate further.

cc: @reid do you have any idea why this would fail in IE8?

ryanseddon avatar Jun 11 '12 02:06 ryanseddon

Hmm... strange. I do not get any feedback :| it just hangs and sits there silently forever.

Btw, waiting until ready and having to hit enter manually doesn't feel convenient, does it?

jayarjo avatar Jun 11 '12 07:06 jayarjo

On a side note, how do you achieve such colorful console experience?

jayarjo avatar Jun 11 '12 07:06 jayarjo

Are you using your own copy of IE8? I think onerror support might be available in BrowserStack IE8 VMs through a plugin.

The colour comes from http://dotfiles.github.com/ specifically this bit https://github.com/mathiasbynens/dotfiles/blob/master/.bash_prompt

ryanseddon avatar Jun 12 '12 01:06 ryanseddon

No, I was running it through BrowserStack VMs. Maybe there is a difference between the versions that we use? I installed bunyip through npm.

Thanks for the color tip :)

jayarjo avatar Jun 12 '12 07:06 jayarjo

I tried IE8 on Windows 7 now, and while it still throws that $yetify error, it is able to report back into the console. I see now that you were trying it IE8 Windows Vista, obviously that's why it succeeded. But it still fails to report and hangs for IE8 XP.

jayarjo avatar Jun 15 '12 09:06 jayarjo

Filed a ticket here: http://yuilibrary.com/projects/yeti/ticket/87

jayarjo avatar Jun 15 '12 11:06 jayarjo

Yeti has moved away from socket.io in their latest release. If you do an npm update bunyip and swap out the qunit adaptor with the latest in the repo see if that makes a difference...

ryanseddon avatar Jun 25 '12 06:06 ryanseddon

I've resolved this issue upstream (yeti) and submitted a pull-request to their team.

jasisk avatar Nov 15 '12 19:11 jasisk