Michael W

@VitaliyOnRule I have not solved the problem. Although it does for some random reason seem to occur far less often.

@emyl3 and @VitaliyOnRule I actually ended up using my server as a "proxy" and loading the image from `base64` 😞. Appreciate the input though.

@riksnelders ooooor, they could just fix the component. 🙁

Yup, I do the following: ``` let minMax = this.calculateAspectRatioFit(resp.newWidth,resp.newHeight,screen.availWidth,screen.availHeight) this.EditorInstance.invoke('resizeCanvasDimension',{width:minMax.width,height:minMax.height}) .then(()=>{ ... }) ``` That all works well. Generally the scaled image ends up being 375x500-ish. It looks great....

Yes, it's based on `screen` as follows: ``` cssMaxWidth: screen.width, cssMaxHeight: screen.height, ```

@jungeun-cho Well, I'm using the wrapper *on* a mobile device (i.e. Cordova). Does the wrapper not include the CSS? When I add new objects, they are tiiiiiiiiiiiiiny. And it doesn't...

@fritx perhaps part of the problem is that `contenteditable` isn't supported for `textarea`? 🤔

@fritx if that's the case, is there a good way to make the `div` look and behave like a `textarea` (e.g. multi-line, word wrapping, etc.)?

@fritx I actually got it working, but for some reason, it's not syncing with `v-model` when the data is re-loaded. The field simply remains visibly empty. Thoughts? 🤔

@fritx Discovered the problem. Apparently the `component` must literally be `v-model` bound to an object named `html`. This needs to be documented but preferably changed. 😖