News for hackers. Stuff that matters.

A comment on Firefox 29. Parent comment

Re:Firefox 29 by angersock on Tuesday April 29, 2014 @04:25PM (#7669743)
Thank you very much for your explanation!

We ended up writing a goofy little console.log() replacement that sent messages back to the main UI thread for processing and logging, but that kind of thunking is a might-bit janky.

[ Parent | on HN ]
Re:Firefox 29 by bzbarsky on Wednesday April 30, 2014 @01:08AM (#7671721)
The console.log exposed to workers just sends the messages to the UI thread for logging...
[ Parent | on HN ]
Re:Firefox 29 by angersock on Wednesday April 30, 2014 @02:09AM (#7671861)
I forget whether the workaround was done for Firefox or Chrome...I remember hitting it in one or the other, and putting in the workaround for both.

On a related note, transferable objects are handled a bit differently between IE, FF, and Chrome. Some are a bit stricter than others.

[ Parent | on HN ]
Re:Firefox 29 by bzbarsky on Friday May 02, 2014 @02:26AM (#7684346)
That's not surprising, but annoying. Please do file bugs as needed; the spec is generally pretty clear about how things should work here, so if browsers don't agree one of them is just buggy.
[ Parent | on HN ]