Geoff Baum

Also looking for this behavior. @Vontus did you have a fork you're working off of?

@fritx so I was able to sort of hack it in there via the `froala.initialized` event like so: ``` 'froalaEditor.initialized': function (e, editor) { this.editor = editor if (this.options.disabled) {...

Can we get this merged in? This is a slightly annoying error.

Also, I was able to hack something by setting the CSS margin-top of the wrapper container to `-137, which appears to be the height of the header. Then, once the...

It's even worse with latest because the build won't even go through. Previously, it just wouldn't generate/add the translations. Now the build spits out these errors: ERROR in ../i18n/web/locale/Component.json?vue&type=custom&index=0&blockType=i18n&issuerPath=src%2Fcomponents%2Fcontainer%2Fworkflows%2Fgrids%Component.vue (./node_modules/@intlify/vue-i18n-loader/lib/index.js!../i18n/web/locale/Component.json?vue&type=custom&index=0&blockType=i18n&issuerPath=%2Fsrc%2Fcomponents%2Fcontainer%FComponent.vue)...

I was able to work around it by adding ``` process.on('exit', () => { throw new Error('Unit tests failed. See above for more information.'); }); ``` to the top of...

Actually, that didn't work. That returns an error code no matter what the exit code is. The problem is, the node execution of the qunit command always returns 0, for...

I got it working, but it's really ugly and painful. I had to call the command line directly using node execSync... yeah. ``` const execSync = require('child_process').execSync; execSync('node-qunit-phantomjs ./src/test/resources/qunit/test1.js.html --verbose',...

Sure, I'll try and look into it further when I get a sec. For the time being, executing the commands directly via an execSync() works. Honestly, it might be just...

+1