If you use the SAPGUI For HTML to show a textedit control on a dynpro screen, it could happen, that this control seems to be too wide. For example it does not fit into a groupbox, or additional horizontal scrollbars appear, with which you can scroll the whole textedit control.
If you compare the Textedit control to that, you get with the wingui, it is bigger in width.
The textedit control has some limitations in SAPGUI For HTML compared with SAPGUI for Windows. One of them is the wordwrap behaviour.
Setting the wordwrap methods of the textedit control will have these results in SAPGUI For HTML:
Method SET_WORDBREAK_PROCEDURE does not work and has no effects on wordwrap behaviour.
value WORDWRAP_OFF does not work and has the same behaviour as
value WORDWRAP_AT_WINDOWBORDER automatical wordwrap at the right edge of the textedit control
value WORDWRAP_AT_FIXED_POSITION automatical wordwrap after a fixed position in the textedit control.
Parameter WORDWRAP_POSITION: determines the position of the wordwrap, if parameter WORDWRAP_MODE has value WORDWRAP_AT_FIXED_POSITION. If the value is set to 0, then the wordwrap will occur at position 72.
Parameter WORDWRAP_TO_LINEBREAK_MODE does not work.
The parameters of method SET_WORDWRAP_BEHAVIOR have the same meaning as the identical parameters of the constructor method.
1.) if the parameter WORDWRAP_MODE has value WORDWRAP_AT_FIXED_POSITION, then the textedit control will have as size the value of the parameter WORDWRAP_POSITION (or 72, if WORDWRAP_POSITION = 0). It will not have the size of the control container, as in wingui. Therefore, if the size of the control container is smaller than the value of the parameter WORDWRAP_POSITION, then the textedit control will overlap his container and will be wider than the textedit control in the wingui.
2.) if the parameter WORDWRAP_MODE has value WORDWRAP_AT_WINDOWBORDER, then the textedit control will have as size the initial size of his container. This size will be fix, even if the container size changes during user actions (perhaps the container is a splitter and the user move this splitter).
This is because of technical restrictions of the HTML textarea element, which is used to render the textedit control in SAPGUI For HTML.
For a solution of 1.) and 2.) please implement the following patches:
ITS 620 patch 23
ITS 640 SAP_Basis support package [see below]
ITS 700 SAP_Basis support package [see below]
Prior to this solution the fix of this technical restriction was in the responsibility of the application developer, who use the textedit control in SAPGUI For HTML, to work with this limitation:
to 1.)Perhaps, he can enlarge parent containers or surrounding groupbox or he can enlarge the textedit control container himself.
Or he can make smaller the value of the parameter WORDWRAP_POSITION, so that he is not bigger as the texxtedit control.
to 2.)Perhaps he can put the textedit control on a fix sized container. Or he accept, that the user has to scroll the textedit control to read his whole content.