Quantcast
Channel: AjaxControlToolkit Work Item Rss Feed
Viewing all articles
Browse latest Browse all 4356

Commented Issue: HtmlEditorControl is not Compatible with TabContainer [26977]

$
0
0
There seems to be a bug when displayed in TabContainers. When not in a TabConainer, the editor looks correct. When within a TabContainer I get the original TextBox displayed and either the HTMLEditor is 1px wide and as long as the page, or right below the TextBox.
Comments: My application uses a "tabcontainer" with six tabs each of which contain a "usercontrol". The "tabcontainer" sits inside a "div" which is only displayed as the result of a user action elsewhere on the page. The fourth tab contains the editor (textbox + extender) and I found, as have others, that the editor rendered as a useless 1px wide. An editor outside the "tabcontainer", of course, rendered correctly. Hence, if I could leave the editor outside the "tabcontainer" located as to be effectively invisible, but move it on on page load to the tab, then, that might be a solution - and it was! My own page design meant that the "div" containing the editor could not be viewed anyway but for those whose page designs do not allow this the solution is as follows: 1. Create a "div",(mine is "divEditorSource") position absolute with a top far beyond the page, say 5000px. This will ensure that the user can not see the editor in its original position but that the editor will be rendered correctly. 2. Create a "div" (mine is "divEditorTarget") inside the appropriate tab where the editor is to show. 3. Add a few lines of javascript to the "onload" event for the page as follows: d_source = document.getElementById("divEditorSource"); d_source.style.position = "relative"; d_source.style.top = "0"; document.getElementById('divEditorTarget').appendChild(d_source); where "divEditorSource" contains the editor and, "divEditorTarget" is on the fourth tab As the input to the editor within my own application is posted via a callback, I can not say whether any issue with the posting of the form remains. One could, of course, merely reverse the above process and move the editor back to the "visible" portion of the document body before submitting the form - just a thought. Hope this helps some of you with your development problems!

Viewing all articles
Browse latest Browse all 4356

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>