tinyMCE 4 instance after mceAddEditor really tall -

-

Pre-Note: This issue occurs if I already have a text on the page or not.

I have a button that first triggers an AJAX request ... writing something for a database and returning the key I use that key in my ID for textarea Which is then dynamically linked to the page. Keep in mind that tinyMCE has already been started. 

  tinymce.init ({selector: ".adder", setup: function (ed) {ed.on ('change', function (e) trigger ('checkform.areYouSure'); }; Ed.on ('init', function (e) {autoresize_max_height: 500})}}, plugins: ["Advlist auto link link responsivefilemanager lists printing preview hours anchor pagebreak spell-checker charmap", "searchreplace wordcount visualblocks Visualchars code fullscreen insertdatetime nonbreaking media "," save table contextmenu directionality template paste textcolor colorpicker responsivefilemanager autoresize "], toolbar:" back again | styleselect | bold italic | forecl "Back to the top" Aligncenter alignright | Balllist number list | Outdent indent | table | link responsivefilemanager ", image_advtab: true, external_file, administrator_path:" / filemanager / ", filemanager_chirt:" filemanager ", external_plugin: {" filemanager ":" / Filemanager / plugin.min.js "},}); After Textarea is dynamically created, I have some default 'Lorem Ipsum' text and call mceAddEditor  
  tinymce.execCommand ('mceAddEditor', incorrect, "custom-html_" + data.c2akey );  
 
 data.c2akey is the key returned by AJAX call. 
 
 The tinnimus instance has been successfully created 
 
  Here's the problem:  
 
 1) This example is super long. Unless I set a fixed height on the original container, the editor is actually long. The problem of setting a static height on parent container is more than 500px ( autoresize_max_height ); The problem is that autorissance works. Besides, I do not see text from Textreria in this new editor. 
 
 2) I can not type in this newly created example.

P> Your first problem (for example, super long) I Resolved as follows: 

  tinymce.init ({... init_instance_callback: function (editor) {$ (editor.iframeElement) .contents () .Fund ('body'). CSS ( 'Min-height', editor.targetElm.rows * 9);}});

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more