Paul

Yeah, I think the best approach right now is to [extend the output of `create()`](https://github.com/dojo/framework/issues/253#issuecomment-464380823). I think the challenge I'm running into is when a widget is part of an...

Thanks for the example. It made it easy to track down the issue. Steps to reproduce are: 1. resize the grid so the column headers are wider than the available...

> How I should scroll page when I write test manually, without "visualTest"? Scrolling doesn't have a consistent implementation across browsers. Even within Chrome, they have changed how the scroll...

Howdy rozaev, I'm seeing ``` Error: Failed to load module fs from /Users/pshannon/sss/intern-visual-demo/fs.js (parent: intern-visual/assert) ``` which means you'll definitely want to use `intern/dojo/node!`. Admittedly it's confusing because the package...

Closed for #2

Sorry, I took a quick look at this one and missed a large part of the problem. `intern-visual` requires a loader that can handle loading both node and AMD modules....

It may be possible to use Intern's default loader. We would need to use an AMD `map` for any node module so it mapped to something like ``` map: {...

A console.warn is nice, but what about calling `getProperties`?

What about `Container`'s responsibility to provide properties to the injected Widget? If you don't call `getProperties` there's no opportunity for defaults to be provided. Then we're back to making all...

If it's truly a bug, a console.warn doesn't help aggregate these errors to a central logging server when in production or help resolve Container's missing property data.