Upload behaviour in Safari, filter improvements

7 posts, 0 answers
  1. Tayger
    Tayger avatar
    191 posts
    Member since:
    Jan 2015

    Posted 08 Jul 2018 Link to this post

    Hello

    I have 2 topics concerning the KendoUI Upload Widget:

    1. Drag of uploaded image in Safari browser (Mac) starts upload

    I have a DIV area onto which users can upload images. In the background I create a thumbnail of that and display it in the mentioned DIV area. Recently I realised in Safari browser (Mac) that if I drag such a displayed thumbnail onto that DIV it will upload that thumbnail too as an image and therefore a copy will be created. I would like to avoid that. Let's say:

    - Ok: Drag images from outside into upload DIV
    - Not ok: Drag thumbnail displayed in the DIV onto the same DIV that starts an upload

    Since this "problem" exists not in Firefox and Safari I assume this is a browser behaviour. Question is if I can check whether a thumbnail will be re-uploaded or an image from outside.

    2. Case sensitive upload validation

    I have created a filter upload be restricting to specific image types:

    allowedExtensions: ['.jpg', 'jpeg', '.png', '.gif', '.svg', '.mp3', '.mp4'],

    It works fine and does what it should. Recently a customer told me he can't upload his JPG-File. I checked that and found out that the extension was uppercased (.JPG). After renaming his image to 'xxx.jpg' I was able to upload the image. That tells me that the extension check is case sensitive. Of course I have enhanced the allowedExtenions list with all valid image extensions in upper case which will cover most situations. But what if someone wants to upload an image called 'image.Jpg'? Technically it is correct but will be prohibited. 

    All over: If it doesn't break the KendoUI security rules it would be nice if the extension check is not checking for case sensitive. 

    Regards

  2. Plamen
    Admin
    Plamen avatar
    3057 posts

    Posted 10 Jul 2018 Link to this post

    Hello,

    One possible way to handle such unwanted selection is to cancel the select event of the upload widget only when the thumbnail  is selected - I possible way is to set some custom name to this thumbnail  so it can not be easily differentiated.

    As for the second issue - this is a nice feature request for the widget - in such case I would recommend you to log it in our feedback portal here.

    Regards,
    Plamen
    Progress Telerik
    Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  3. Tayger
    Tayger avatar
    191 posts
    Member since:
    Jan 2015

    Posted 10 Jul 2018 in reply to Plamen Link to this post

    Thank you, I will consider your solution to identify the thumbnails.

    Feature request: I expected that answer. Waste of time from customer perspective. The chance it will be implemented is close to 0, so I don't use that system and live with the workaround.

    Regards

  4. Plamen
    Admin
    Plamen avatar
    3057 posts

    Posted 11 Jul 2018 Link to this post

    Hello,

    Thank you for getting back to us and for providing your feedback.

    Our roadmap and priorities depend largely on the business value and customer demand for specific components and features. That is the reason we have voting for the features in the feedback portal and that is how we determine the priority and plan which features will be added.

    Regards,
    Plamen
    Progress Telerik
    Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  5. Tayger
    Tayger avatar
    191 posts
    Member since:
    Jan 2015

    Posted 16 Jul 2018 in reply to Plamen Link to this post

    Sadly, there is no proper solution: When dragging a thumbnail (already uploaded image) into upload area the "new" image will always be called image.<extension>. Of course I could now block images with name "image" but that would confuse users. I have checked all other values in the incoming object of the select option. There are no official differences to differ between new uploaded file and dragged thumbnails. Something I obviously have to live with it and is of the same "not so nice" as the upper/lower case problem when uploading a file.
  6. Tayger
    Tayger avatar
    191 posts
    Member since:
    Jan 2015

    Posted 16 Jul 2018 in reply to Plamen Link to this post

    Concerning your roadmap and what customer wants: Of course you need a roadmap, I completely understand this. On the other side I've heard that mantra already so many times. Most problems in that vote system are so customer specific that nearly no one else cares about and would vote for it. Normally users will go there IF they have a concrete problem they want to have solved.

    Otherwise you need customers to bring onto the vote system. Then they have to search into it or go through a big list... Ppl are busy with other things... So how big is the chance to get a feature implemented? Far below 1%? Probably around that. Will I waste my time for entering? No....I've already entered some: None were implemented and most feature request have only the votes of the creator itself.

    Just to prove you're wrong I have added this feature request right now even by knowing it will never be implemented by that "voting system" even if it makes so much sense to correct this. 

    Regards

  7. Plamen
    Admin
    Plamen avatar
    3057 posts

    Posted 18 Jul 2018 Link to this post

    Hello,

    For the first issue with the Safari thumbnails another possible solution is to prevent dragstart of the thumbnail as for example it is described here

    Yes indeed you are right some of the more exotic feature requests are not getting many likes yet we are reviewing them and if any of them seem valuable for many cases we could implement them even they don't have many votes. 

    We also understand that some of the requests could be very important for some of the customers yet we as a vendor are trying to use our resources mainly for the most important features and that is why voting is the primary way for prioritization.

    Regards,
    Plamen
    Progress Telerik
    Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
Back to Top