Since upgrading to Chrome 51, I’m now seeing this error occasionally when switching routes (I’m using FlowRouter):
“The basic HTML.TransformingVisitor does not support foreign objects in attributes. Define a custom visitAttributes for this case.”
Once I get this error, no further route switches will work until the page is refreshed. Is anyone else experiencing this? There’s an issue opened but it doesn’t seem to have gotten much activity so I’m wondering if there’s something unusual I’m doing.
Yes, also seeing this in Google Chrome v51.0.2704.63 (64-bit). It just started occurring. No code changes on our end w/r/t my Meteor sources.
From the JS Developer console:
Error: The basic HTML.TransformingVisitor does not support foreign objects in attributes. Define a custom visitAttributes for this case. at visitAttributes (2457910….js?meteor_js_resource=true:83) at visitAttributes (2457910….js?meteor_js_resource=true:89) at Object.f._expandAttributes (2457910….js?meteor_js_resource=true:89) at p (2457910….js?meteor_js_resource=true:89) at 2457910….js?meteor_js_resource=true:89 at Function.e._withTemplateInstanceFunc (2457910….js?meteor_js_resource=true:91) at 2457910….js?meteor_js_resource=true:89 at Object.f._withCurrentView (2457910….js?meteor_js_resource=true:89) at c (2457910….js?meteor_js_resource=true:89) at o.Computation._compute (2457910….js?meteor_js_resource=true:21)
No, it is not reproducible every time, it seems to be random.
Sometimes when you follow a link inside the application, the page is not displayed and you have this error in the console.
So you reload the page (F5) and the page is displayed. Then you try the same navigation scenario as when the error occurred, but you can not reproduce it. Frustrating.
Using iron-router and Meteor 1.3.2.4 and just encountered it:
5d3b926….js?meteor_js_resource=true:3 Exception from Tracker recompute function:
5d3b926….js?meteor_js_resource=true:3 Error: The basic HTML.TransformingVisitor does not support foreign objects in attributes. Define a custom visitAttributes for this case.
at visitAttributes (5d3b926….js?meteor_js_resource=true:88)
at visitAttributes (5d3b926….js?meteor_js_resource=true:94)
at Object.f._expandAttributes (5d3b926….js?meteor_js_resource=true:94)
at p (5d3b926….js?meteor_js_resource=true:94)
at 5d3b926….js?meteor_js_resource=true:94
at Function.e._withTemplateInstanceFunc (5d3b926….js?meteor_js_resource=true:96)
at 5d3b926….js?meteor_js_resource=true:94
at Object.f._withCurrentView (5d3b926….js?meteor_js_resource=true:94)
at c (5d3b926….js?meteor_js_resource=true:94)
at o.Computation._compute (5d3b926….js?meteor_js_resource=true:38)
This happened on a computer running Windows 7 and Chrome 51.0.2704.84.
Refreshing the page fixed it. It happened randomly and I have no idea how to reproduce it.
@sashko Is it possible for someone at MDG to look at this issue? Between the forum and the GitHub issue it seems to be widespread and a significant problem even though none of us have been able to formally reproduce it.