Using RadEditor (http://demos.telerik.com/aspnet-ajax/editor/examples/custommodules/defaultcs.aspx), when placing two of them on one page the following occurs:
The first one works perfectly.
The second one works but when styling or doing anything to it the HTML source is full of only plain text, no styling whatsoever.
Is there an issue using two RadEditor's with the one control even if they are uniquely named?
What possible solutions could I implement to fix this issue?
Thanks.
Well, what is the code that is causing the problem? Copying over several editors from the demo you linked has them working properly with me. Check your implementation for global variables or weird names (in function, variables, the module itself, etc).
Related
I often have a problem where I'm working on a dynamic web app with tons of front-end or back-end code and there is a CSS problem that just eludes me despite an hour of scratching my head. I know that StackOverflow could solve it in a second, and I'd like to post it, but I either have to
Make the app public along with steps to reproduce the state, or
Tediously copy out the DOM and assets (CSS) along with the current state.
Neither is very straightforward. Note that the DOM is dynamically generated so "View Source" won't cut it. Similarly, the CSS could be spread out across multiple files and I'd like to just grab it all at once.
Is there an easy way to copy out the DOM and all CSS as a single file so that I can insert it into something like JSFiddle and be on my way?
The quickest way to get all HTML on the page as-is is to paste this in the address bar:
javascript:alert(document.body.outerHTML)
You can also use the console, of course, but the above works even in old IE versions and is easier to copy/paste.
I don't think there's a good way to get the CSS at all, but you could try using a jQuery selector or similar to get the URLs:
$('link[type="text/css"]')
.each(function(x, link){
console.log(link.attributes.href.value)});
And downloading and concatenating the CSS.
Requirement : I need editable drop down in my application similar to the one in the given here.
In my existing application I am using jQuery Data table within this table I need one of the column to be editable drop down.
For this I Googled it and found jQueryUI AutoComplete ComboBox,I gone through the demo and I changed it according to my requirement but I didn't find any changes.
Even I am not able to understand whether cause/problem is ude to Data Table or jQueryUI/autocomplete library.
FYI,
I have included
jquery-ui.js
jquery.dataTables.min.js (datatable)
js/jquery-1.9.1.js
css/style.css
if any one come across this problem please guide me.
Before configure this in your application ,please try this in a different file. i have tried this code and works . May be some other script files in your application affected this JQ.
Visited http://www.12titans.net/p/s/register.aspx, right click view source on the page .I found the html source so compact,have no blank. How to do like this in asp.net?
I am use IE8 ,tks in advance! sorry for my bad english!
I have the same problem with debugging some spring mvc projects, What i normally do is use chrome, right click on the page and inspect element. The element explorer is the source code with javascript applied to it, so i might be a little different, but normally for the better
hope this answer your question.
When you generate HTML using ASP.NET, just don't insert tabs or line breaks or spaces in the source code, and when you code HTML by hand, do the same thing.
In other words, do it by hand.
You can also use a DOM Parser which should be able to get the bare necessities and print it out without any tabs or whitespace.
due to lack of documentation about this feature i can't find a way to do this. I am trying to use autoLoad with merge mode. I have a TabPanel in which each tab is supposed to open autoloading another page using merge mode.
i am aware that plain HTML does render, but pages including Ext.net components fail to render. In my child page i have a resource manager registered with RenderScripts set to 'None' Ext.Net examples page shows a merge mode example in that way.
Right now i get a 'Ext.net.Store is not a constructor' in the child page.
Is there any special parameter which needs to be sent in the loadConfig when doing the autoload? or are there any special elements besides resource manager needed on the child page?
Using <AutoLoad Mode="Merge" /> is very tricky. In general I'd say it should be avoided, with preference given to using 'XRender' functionality or <AutoLoad Mode="IFrame" />.
It's tough to say exactly what's going wrong in your code. Posting a simplified sample demonstrating how you have things configured and demonstrating how to reproduce the problem would be very helpful.
I have a view that I created based upon a content type in my drupal instance. I have then went and added some exposed filters. Two of these filters are date fields that use the jquery ui datepicker popup. Functionally, everything is working fine. Aesthetically, everything is not fine....
With the date picker, The label is showing up in the correct place, but the actual text box where the date will ultimately display is dropped down to the next line. Has anyone worked with this module that might be able to give me an idea of where the issue might be? If I just put a regular exposed filter on (that works with regular text fields instead of dates), it works fine.
This leads me to believe it is something to do with the module css, but I don't know where else to look.
Thanks for any thoughts.
I suspect your problem might actually be in your theme. There might be a class definition that's overruling the module's definitions and throwing the layout off.
If you switch your page to Garland and the problem goes away, then you'll know you need to look in your theme to find the offending element. Firebug and similar tools will help you find that quickly.
The default CSS in that whole suite of Date-related modules is pretty robust, in my experience. I've thrown them into some pretty hairy page layouts and they've always performed admirably, so the module's CSS is probably the last place I'd look for a problem.