Bug 310773 - KDialog does not allow use of the HTML5 attribute "accept" for creating file masks on upload inputs.
Summary: KDialog does not allow use of the HTML5 attribute "accept" for creating file ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdialog
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Brad Hards
URL: http://jsfiddle.net/fbqKH/
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-11-27 17:03 UTC by Chris
Modified: 2018-10-27 04:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2012-11-27 17:03:50 UTC
KDialog does not allow use of the HTML5 attribute "accept" for creating file masks on upload inputs.

If you have a input such as (reproducable here: http://jsfiddle.net/fbqKH/ ):

<input type="file" accept="image/*" name="uploadedfiles" multiple=true >​

And then you select attempt to select a file, KDialog defaults the file file view to "All Supported Files" and also adds an additional "unknown" file type. 

Expecpected behaviour would be to default to the file mask type as provided in the input. 

Reproducible: Always

Steps to Reproduce:
1. Launch Chrome
2. View <input type="file" accept="image/*" name="uploadedfiles" multiple=true >​
3. Click the button. 
Actual Results:  
THe expected file mask is hidden.

Expected Results:  
It would be expected that by default only files of MIME type "image/*" displays first. 

I'll mark this as a minor loss of function. It's my first time submitting a KDE bug report, so if this is an actual bug, please upgrade it as such.
Comment 1 Christoph Feck 2012-11-27 21:21:57 UTC
What command line arguments are used to call kdialog? If unsure, ask Chrome developers. See also bug 295820.
Comment 2 Chris 2012-11-28 09:32:43 UTC
I'm not sure how to find out that information, but I have submitted a bug report with Chromium.

I don't believe that this is a KDialog bug any more, and is most likely a problem with how Chrome invokes the dialog as you suggested. 

http://code.google.com/p/chromium/issues/detail?id=163082
Comment 3 Andrew Crouthamel 2018-09-23 02:42:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 04:08:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!