QualiWareUA
Top achievements
Rank 1
Rank 1
QualiWareUA
asked on 28 Jan 2009, 03:50 PM
Hello,
There is a documentation on how to create non-editable areas - http://www.telerik.com/help/aspnet-ajax/editableandnoneditableareasineditor.html. I can do this in editor. But in case of IE there are small rectangles around the non-editable element (used for resizing). And in this case they are useless and inappropriate, I would say. Is there a way to remove them? As well as change mouse pointer to default? I could do this with css style. So any help will be appreciated!
There is a documentation on how to create non-editable areas - http://www.telerik.com/help/aspnet-ajax/editableandnoneditableareasineditor.html. I can do this in editor. But in case of IE there are small rectangles around the non-editable element (used for resizing). And in this case they are useless and inappropriate, I would say. Is there a way to remove them? As well as change mouse pointer to default? I could do this with css style. So any help will be appreciated!
3 Answers, 1 is accepted
0
Hi,
The observed small rectangle handlers around the DIV element are displayed by the browser itself and they cannot be hidden by javascript code or css style. Such handlers are automatically displayed around a selected image, table or element that has a hasLayout. layout.
Best regards,
Rumen
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
The observed small rectangle handlers around the DIV element are displayed by the browser itself and they cannot be hidden by javascript code or css style. Such handlers are automatically displayed around a selected image, table or element that has a hasLayout. layout.
Best regards,
Rumen
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Kevin
Top achievements
Rank 2
Rank 2
answered on 13 Feb 2009, 08:23 PM
Hmmm this is interesting. I reviewed the link provided:
http://www.telerik.com/help/aspnet-ajax/editableandnoneditableareasineditor.html
That could have some real use. However, in actual implementation there would be more to it. For example, if you wanted to implement a working ability to edit only portions of a page in the editor, you'd have to somehow strip out the div tags with the editable/non-editable information before a page is actually published right? I mean you wouldn't leave those divs and tags in the final web page would you?
I didn't know this feature was even available so it looks interesting! Just trying to think how it might actually be used.
http://www.telerik.com/help/aspnet-ajax/editableandnoneditableareasineditor.html
That could have some real use. However, in actual implementation there would be more to it. For example, if you wanted to implement a working ability to edit only portions of a page in the editor, you'd have to somehow strip out the div tags with the editable/non-editable information before a page is actually published right? I mean you wouldn't leave those divs and tags in the final web page would you?
I didn't know this feature was even available so it looks interesting! Just trying to think how it might actually be used.
0
Hello Kevin,
There should not be any problem keeping those tags even in "public" mode - after all, then content is not editable anyway.
Kind regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
There should not be any problem keeping those tags even in "public" mode - after all, then content is not editable anyway.
Kind regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.