Resizing of Word Processor control

[Philip]

I've experimented with the Word Processor control and searched for posts about it here, and while I'd like to try to use it, I'm disturbed by what appears to be a lack of proper handling of resizing, and also a lack of documentation other than the API, which isn't trivial to map to Razor format.

As far as I can tell, there's some undocumented behavior in the Syncfusion Javascript library handling the controls which detects browser resizing and updates the control, internally. The control does not appear to be able to fit itself inside of a container and then naturally resize itself per the usual expectations via CSS. This is a showstopper problem. What's a clean, documented solution?

Furthermore, the formatting sidebar, fixed to the right and taking up tons of width, is ugly and non-standard. Others have said as much. Why isn't a much more standard and expected second toolbar row used instead?

As well, the existing top toolbar row is excessively large, and not attractive. 

It's a shame that a component with so much functionality is undercut by what seem to be easy to fix cosmetic issues by Syncfusion. Any chance that'll happen soon?

[Kurthis Banu Abdul Majeeth]

Hi Philip, 

We have cross checked your reported problem. We have added some changes in resize related for blazor word processor component in latest release.  

For properties pane (Side Pane) :  

DocumentEditorContainer component have predefined toolbar and properties pane to view and modify word document. It doesn’t have support for access and customize the Properties pane. So, whenever resize the DocumentEditorContainer component PropertiesPane doesn’t resize because of, it has predefined width.  

Toolbar and Editor will be resize based on window resize and Scroll arrow icon will be enable. 

So, could please check with latest blazor nuget version 19.3.0.56 and let us know if you have faced any issues. Kindly share us more detail about the reported problem such us screenshot or video demonstration of the reported problem, which will be helpful for us to investigate further and provide you the solution at the earliest.  

Please let us know if you have any questions.  

Regards, 

Kurthis Banu A. 

[Philip]

When the Word component is placed inside of the right pane of a Splitter control, and the browser window width is dragger wider, the Word window expands, but it never contracts again when the browser window width is dragged narrower again. That's one observed problem.

Another issue is the padding between the content and the container. I don't see a way to control the amount of padding, nor the width of the content "window" itself (I put "window" in quotes because browser debugging does not show a particular DIV for the content.)

[Kurthis Banu Abdul Majeeth]

Hi Philip, 

We have cross checked your reported scenario. In latest version we have faced Toolbar scroll arrow does not enable. So, we need some additional details to reproduce the exact issue ,could you please share us the below things at your end? 

1.       Screenshot of the issue 

2.       Video demonstration of issue  

3.       Syncfusion product version which you are using in your application. 

This will be more helpful to reproduce the same issue at our end. Thereby, we will proceed further on the reported issue and provide you the appropriate solution at the earliest. 

Regards, 

Kurthis Banu A. 

[Philip]

I've tried the Rich Text Editor in place of the Word component and both the toolbars and resizing are exactly what I'd expect without some hassle to handle what should already be built-in, so I'll be using that for now - I don't have the time or patience to debug the Word component. I encourage Syncfusion to make improvements to the Word component UI to make it more usable.

[Kurthis Banu Abdul Majeeth]

Hi Philip,  

Apologies! 

If possible, can you please share your exact use case scenario in which you were faced resizing related issue with screenshots? that will be helpful for us to improve Document editor components if any issue. Also, possible we will share solution for the issue. 

Regards, 

Kurthis Banu A.