236981 2022-02-21 10:19:35 -0800 [iOS] Crash when selecting the "Take Photo" file picker menu item if the app doesn't have the necessary entitlements 2022-02-26 22:47:18 -0800 1 1 1 Unclassified WebKit HTML Editing Safari Technology Preview iPhone / iPad iOS 14 NEW InRadar P2 Major --- 1 weaksdfg webkit-unassigned akeerthi webkit-bug-importer wenson_hsieh oldest_to_newest 1844256 0 weaksdfg 2022-02-21 10:19:35 -0800 Individual attributes "capture" can't disable the "take photo" on IOS but Android can disable this https://stackoverflow.com/questions/23234596/how-to-disable-capture-when-upload-image-file-using-safari-on-ipad 1845358 1 webkit-bug-importer 2022-02-23 15:37:30 -0800 <rdar://problem/89382404> 1845382 2 akeerthi 2022-02-23 15:51:08 -0800 The "Take Photo" action is displayed whenever image types are accepted by the file input, and is independent of the "capture" attribute. The spec doesn't say that we should exclude such an option if "capture" is not specified. Can you elaborate on why you want to disable this action? 1845580 3 weaksdfg 2022-02-24 04:32:08 -0800 (In reply to Aditya Keerthi from comment #2) > The "Take Photo" action is displayed whenever image types are accepted by > the file input, and is independent of the "capture" attribute. The spec > doesn't say that we should exclude such an option if "capture" is not > specified. > > Can you elaborate on why you want to disable this action? sir, The file input is not of type picture, but "Photo" still shows up, then Clicking "take a photo" on an html page will crash the app, even if the app doesn't have permission to open the camera. My project has webview in an APP, happens as described earlier. So I think there has to be a feature to disable it off 1845865 4 akeerthi 2022-02-24 17:59:12 -0800 (In reply to alexhsu from comment #3) > (In reply to Aditya Keerthi from comment #2) > > The "Take Photo" action is displayed whenever image types are accepted by > > the file input, and is independent of the "capture" attribute. The spec > > doesn't say that we should exclude such an option if "capture" is not > > specified. > > > > Can you elaborate on why you want to disable this action? > > sir, > The file input is not of type picture, but "Photo" still shows up, then > Clicking "take a photo" on an html page will crash the app, even if the app > doesn't have permission to open the camera. > My project has webview in an APP, happens as described earlier. > > So I think there has to be a feature to disable it off Thanks for the explanation. We currently show "Photo" options unless the input explicitly excludes images via the "accept" attribute. This means that a plain <input type=file> will always show the "Take Photo" item. I think we should consider removing the menu item in WebKit if the app doesn't have the necessary permissions. Retitling the bug to reflect the issue more clearly. Please let me know if I have misinterpreted something. 1846373 5 weaksdfg 2022-02-26 22:47:18 -0800 (In reply to Aditya Keerthi from comment #4) > (In reply to alexhsu from comment #3) > > (In reply to Aditya Keerthi from comment #2) > > > The "Take Photo" action is displayed whenever image types are accepted by > > > the file input, and is independent of the "capture" attribute. The spec > > > doesn't say that we should exclude such an option if "capture" is not > > > specified. > > > > > > Can you elaborate on why you want to disable this action? > > > > sir, > > The file input is not of type picture, but "Photo" still shows up, then > > Clicking "take a photo" on an html page will crash the app, even if the app > > doesn't have permission to open the camera. > > My project has webview in an APP, happens as described earlier. > > > > So I think there has to be a feature to disable it off > > Thanks for the explanation. > > We currently show "Photo" options unless the input explicitly excludes > images via the "accept" attribute. This means that a plain <input type=file> > will always show the "Take Photo" item. > > I think we should consider removing the menu item in WebKit if the app > doesn't have the necessary permissions. Retitling the bug to reflect the > issue more clearly. Please let me know if I have misinterpreted something. yes, as you describe Mainly want to be able to control this property I would like to ask about the approximate date of this bug timeline?