ImageEditor, crop big image issue in IE

12 posts, 1 answers
  1. Tonci
    Tonci  avatar
    22 posts
    Member since:
    Oct 2007

    Posted 10 Dec 2008 Link to this post

    We are using RadEditor Provider (Telerik.DNN.Modules_2008_3_1125_dev.zip) in DNN 4.9.0.

    ImageEditor is great feature but we have problem with Crop on big image when we are using it in IE.
    It crops wrong part of the image if image is bigger than ImageEditor window and we need to use scrollbar to place crop marks somewhere in right bottom part of the big image.

    This is working OK in Firefox, but in FF we have problem with flip and rotate that do not displays preview of it in ImageEditor when flip or rotate is selected.

    Is there any solution?
    Kind regards
    Tonci
  2. Answer
    Tervel
    Admin
    Tervel avatar
    1337 posts

    Posted 15 Dec 2008 Link to this post

    Hello Tonci,

    Thank you for bringing the issue with cropping large images to our attention. Indeed the behavior can be improved. We logged it for fixing and the next service pack (SP2) for RadControls Q3 2008 will feature a better cropping implementation. I am not able to give you an exact date for the SP yet, but most likely it will be sometime early January.

    As far as the other two issues reported: flip and rotate do work in FireFox - only that the image is not instantly updated on the client-side (it is, however, flipped and rotated on the server, when saving it). This is not a bug, but rather the lack of proper support of FireFox for doing tricks such as flipping and rotating using client code. Now that FF 3 is out, there are some new CSS and Canvas improvements to the FF engine, and it might be possible to implement the clientside functionality properly.

    Best regards,
    Tervel
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Albert Shenker
    Albert Shenker avatar
    550 posts
    Member since:
    Mar 2004

    Posted 31 May 2009 Link to this post

    FYI, in the latest controls update (Q1 2009 527), the rotate/flip issue still exists in Firefox, version 3.

    Also, in the Image Editor, the Opacity % box is still not quite wide enough for 100% to be fully shown.
  5. John
    John avatar
    1 posts
    Member since:
    Feb 2009

    Posted 23 Jun 2009 Link to this post

    has the large image crop issue been resolved yet?
  6. Tervel
    Admin
    Tervel avatar
    1337 posts

    Posted 01 Jul 2009 Link to this post

    Hi everyone,

    In the coming Q2 2009 (about to be released any moment now), the issue has been resolved. You will soon be able to check for yourselves :)

    Best 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.
  7. Stuart Wilson
    Stuart Wilson avatar
    2 posts
    Member since:
    Jan 2009

    Posted 26 Nov 2009 Link to this post

    the flip/rotate under FF still sppears to be an issue.

    was this fault rectified? as it is still apparent even when using the Telerik demos (http://demos.telerik.com/aspnet-ajax/editor/examples/filemanagers/defaultcs.aspx)


  8. Rumen
    Admin
    Rumen avatar
    12846 posts

    Posted 30 Nov 2009 Link to this post

    Hi Stuart,

    It appeared that this feature is not easy to be implemented in Firefox and we postponed its implementation for future time. Unfortunately, I cannot give you a time estimate when exactly this will be available because there are features with high priority logged for Q1 2010.

    Sincerely,
    Rumen
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  9. Albert Shenker
    Albert Shenker avatar
    550 posts
    Member since:
    Mar 2004

    Posted 30 Nov 2009 Link to this post

    This issue doesn't directly affect me right now, but it might in the not too distant future. When it comes to Teleirk addressing this issue, I fear "a future time" means never, or at least not for a couple years. I don't have a firm grasp on how a high-priority issue is decided on, so I can't make any comment about why this is not considered one, however, I do think it would benefit us developers if Telerik did two things.

    1) Be up front about when something like this will be addressed. It may not be in the works for Q1 2010, but does that mean it will definitley be looked at in Q2 2010? I think the answer is no. There are always new high priority items that come up that push things like this down the line. If you never make this a high priority, it is likely going to get pushed off for a very long time. If that is the case, then say it, so developer don't "wait" for this. It may not look good to some, but I assure you as a developer, I would rather be told not to expect a resolution, than be told to expect one and not get it, or be told "who knows".

    2) I think Teleirk has done a good job of creating cross-browser controls, and I can't off the top of my head, think of another scenario where one of their controls' functionality doesn't work at all in one browser or another. I can understand that in certain cases, it might be very difficult to implement a piece of functionality cross browser. In these scenarios, particularly if the functionality is affected in one of the lesser-used browsers, the best solution for a developer (other than fixing the issue), is to prevent the end-user experiencing the problem. In the case of the image manipulation issue addressed in this thread, if the end user is using Firefox, they should not even see options to flip/rotate the image. It would be nice if the Telerik controls were able to determine the browser version on their own and "hide" these options if an incompatible browser is being used. Perhaps the developer should even be given the choice to "hide" or "disable" the options in this case. If a solution like this can't be embedded into the controls, then Telerik should provide an example of KB article on how to do it.
  10. Rumen
    Admin
    Rumen avatar
    12846 posts

    Posted 02 Dec 2009 Link to this post

    Hi guys,

    All bug reports and feature requests are logged in our internal issue tracking system with priority, which depends on a number of factors like:
    • how many users requested / reported the issue
    • difficulty of implementation
    • cross browser support
    • usability that the feature will bring to the control
    • whether the implementation of the feature will slow down the loading of the control
    • etc
    Since we want to make the things more transparent to our users, we are currently working on a new public issues tracking system where our community will be able to vote and raise the priority of the logged issues. We are targeting a release date for this system around the end of December' 09.

    This means that you will be able to vote soon for this Firefox problem and raise its priority to high.

    Kind regards,
    Rumen
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  11. Albert Shenker
    Albert Shenker avatar
    550 posts
    Member since:
    Mar 2004

    Posted 02 Dec 2009 Link to this post

    The public issue voting sounds like a good idea, but I think the only way it will be effective is if you provide some sort of link to the specific issue within the voting interface, right in the Forum or support threads. If a forum or support thread discusses a known issue, then users who submitted the support ticket, or others who found the forum thread through a search, ought to be able to vote on the importance of the issue. Its very rare that users are aware that a "known" issue is causing their problem, so these people will have no other way of voting, unless there is some mechanism or link directly in the forum thread.
  12. Rumen
    Admin
    Rumen avatar
    12846 posts

    Posted 03 Dec 2009 Link to this post

    Hi Albert,

    Once the public issue tracking system becomes available for the community, I will post a link to the logged issue in this forum thread and you will be able to vote for it.

    Best regards,
    Rumen
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  13. Albert Shenker
    Albert Shenker avatar
    550 posts
    Member since:
    Mar 2004

    Posted 03 Dec 2009 Link to this post

    OK. I think Telerik will need to come up with some standard process for doing the same in other threads as well.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017