Hi
We have noticed that when using the spellcheck the popup is displayed over the bottom few pixels of the offending word. Is there a way to configure the offset?
Also when the offending word is near the bottom of the text window, the popup covers the whole word. Again is there a way to either scroll the text into view, or make the popup more clever with regards to it's positioning.
Thanks
David
We have noticed that when using the spellcheck the popup is displayed over the bottom few pixels of the offending word. Is there a way to configure the offset?
Also when the offending word is near the bottom of the text window, the popup covers the whole word. Again is there a way to either scroll the text into view, or make the popup more clever with regards to it's positioning.
Thanks
David
1 Answer, 1 is accepted
0
Hi David,
Up to your questions/comments:
1. Spellcheck dropdown positioning a bit upwards.
There is no property to control the offset of this dropdown. Its code is written in a way that should position the popup right under the wrong word itself. We are not sure what could be causing the incorrect calculations, but it might be some (global) css that you are using on your pages. Are you able to reproduce this behavior on the RadEditor online demo here: http://demos.telerik.com/aspnet-ajax/editor/examples/default/defaultcs.aspx ?
Perhaps opening a support ticket and sending us a working project (or live URL or at least some screenshots of the behavior) will help us determine the origin of the problem.
2. Spellcheck popup near the bottom of the browser window positions above the wrong word, thus obscuring it.
This is a known behavior of the drodpown. To reduce the code for its implementation, the current popup behavior is to simply make sure that the popup does not leave the screen, even if its x and y are set in way that it will do so. Rather, in this case, the popup substracts the difference from the bottom of the screen and repositions on a new location. A more flexible approach (but requiring more code as well) would be to provide more intelligent behavior - such as making sure it does not obscure the wrong word - but renders above it or to its side if necessary. This has already been logged in our TODO list, but has not been implemented yet. I am not able to give you an ETA on this request. The editor featrues and changes are made depending on their priority (e.g. the number of people that report a feature or the number of support a particular problem generates). This particular problem has been with a relatively low priority - but if more people comment on this being a problem for them, its priority will be raised.
Sincerely yours,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Up to your questions/comments:
1. Spellcheck dropdown positioning a bit upwards.
There is no property to control the offset of this dropdown. Its code is written in a way that should position the popup right under the wrong word itself. We are not sure what could be causing the incorrect calculations, but it might be some (global) css that you are using on your pages. Are you able to reproduce this behavior on the RadEditor online demo here: http://demos.telerik.com/aspnet-ajax/editor/examples/default/defaultcs.aspx ?
Perhaps opening a support ticket and sending us a working project (or live URL or at least some screenshots of the behavior) will help us determine the origin of the problem.
2. Spellcheck popup near the bottom of the browser window positions above the wrong word, thus obscuring it.
This is a known behavior of the drodpown. To reduce the code for its implementation, the current popup behavior is to simply make sure that the popup does not leave the screen, even if its x and y are set in way that it will do so. Rather, in this case, the popup substracts the difference from the bottom of the screen and repositions on a new location. A more flexible approach (but requiring more code as well) would be to provide more intelligent behavior - such as making sure it does not obscure the wrong word - but renders above it or to its side if necessary. This has already been logged in our TODO list, but has not been implemented yet. I am not able to give you an ETA on this request. The editor featrues and changes are made depending on their priority (e.g. the number of people that report a feature or the number of support a particular problem generates). This particular problem has been with a relatively low priority - but if more people comment on this being a problem for them, its priority will be raised.
Sincerely yours,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.