You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This caused a follow-up error, which always occurs when Template A is removed:
09:56:33.315 Exception from Tracker recompute function: [meteor.js:1064:23](http://localhost:3000/packages/meteor.js?hash=b9ec8cf25b6fc794ae6b825f30e06c3c35c50e7c)
09:56:33.315 TypeError: domrange is undefined [meteor.js:1064:23](http://localhost:3000/packages/meteor.js?hash=b9ec8cf25b6fc794ae6b825f30e06c3c35c50e7c)
09:56:33.315 doMaterialize@http://localhost:3000/packages/blaze.js?hash=4e97ea5149f9400d1971a350b259a60cb2bf73a5:1952:11
This also causes no other Template to be drawn afterwards, although they should! Should I take hands on this issue? I think this is crucial to a proper user experience.
on Created - Prod
In production it's worse since nobody knows where this comes from:
10:18:08.468 Exception from Tracker recompute function: [144eb911d5f3d4749cb2bd08d2ac42cc9e2c7110.js:1:6618](http://localhost:3000/144eb911d5f3d4749cb2bd08d2ac42cc9e2c7110.js?meteor_js_resource=true)
10:18:08.468 TypeError: o is undefined [144eb911d5f3d4749cb2bd08d2ac42cc9e2c7110.js:1:6618](http://localhost:3000/144eb911d5f3d4749cb2bd08d2ac42cc9e2c7110.js?meteor_js_resource=true)
10:18:08.469 t@http://localhost:3000/144eb911d5f3d4749cb2bd08d2ac42cc9e2c7110.js?meteor_js_resource=true:144:21604
This is something we definitely need to tackle! I think this will be much better, when we integrate #368
The text was updated successfully, but these errors were encountered:
Reproduction
Create a new project
Then manually added
[email protected]
(or once release[email protected]
) to.meteor/packages
Then replaced
client/main.html
with the following:and the following code in
client/main.js
:Here Are my results
on Created - Dev
This caused a follow-up error, which always occurs when Template A is removed:
This also causes no other Template to be drawn afterwards, although they should! Should I take hands on this issue? I think this is crucial to a proper user experience.
on Created - Prod
In production it's worse since nobody knows where this comes from:
And the DOMRange error is completely obfuscated:
This is something we definitely need to tackle! I think this will be much better, when we integrate #368
The text was updated successfully, but these errors were encountered: