Knockout: Deprecation Issue, document.origin

Created on 23 Aug 2018  Â·  3Comments  Â·  Source: knockout/knockout

Just got this warning in the console when using the ko.toJS() method,

document.origin is deprecated and will be removed in M70, around October 2018. Please use self.origin (window.origin) instead. See https://www.chromestatus.com/features/5701042356355072 for more details.

Anyone aware of this? the timeline seems a little short.

Most helpful comment

Thanks @mcarpenterjr — great to hear the problem lies elsewhere, and I hope you get it sorted.

All 3 comments

Thanks @mcarpenterjr ; I can't seem to reproduce this. It would be odd if toJS were accessing document.origin in the ordinary course. Can you please provide a minimal test case?

I'm having some trouble creating a test case for it at the moment, the conditions it occurred under seem to be very specific. But after scanning the knockout repo it looks like there is no use of document.origin. So at this point, I'm guessing it's another library not in compliance. Thanks for the quick response, sorry there's not more here.

Thanks @mcarpenterjr — great to hear the problem lies elsewhere, and I hope you get it sorted.

Was this page helpful?
0 / 5 - 0 ratings