DOM is null about ngx-modialog HOT 3 CLOSED

I don't know what's going on. That doesn't work for me. DOM imported from angular2/src/platform/dom/dom_adapter is always null, even though the makeCurrent function is running. It must be something to do with module resolution in my project. Although it seems odd to me that you would be able to reassign an exported reference (the DOM global) at all. (Disclaimer: I'm new to this stuff.)

Best guess is that the exported variable is somehow associated with an import/module path, and maybe it's exported in more than one place, so there is possibly more than one reference to it, only one of which is being updated by setRootDomAdapter? In that case it could be related to issue #40.

This code, right above the bootstrap call, prints 'DOM: null'.

BrowserDomAdapter.makeCurrent();
import {DOM} from 'angular2/src/platform/dom/dom_adapter';
console.log('DOM:', DOM);

The best I can do seems to be to instantiate my own BrowserDomAdapter and use it instead of this DOM global.

from ngx-modialog.

Strange, you can look at the demo, or even batter at the code generator and you will see it works there.

I'm not happy with the DOM adapter direct use, it's a temp workaround to support adding a class to the body.

from ngx-modialog.

BTW, if you want DOM to be the current DOM adapter
call BrowserDomAdapter.makeCurrent(); before bootstrapping, this is the right way.

from ngx-modialog.