181081 2017-12-21 03:06:36 -0800 Dropping multiple files to Safari changes the file counter to 0 2019-04-03 11:32:01 -0700 1 1 1 Unclassified WebKit WebKit Misc. Safari Technology Preview Mac macOS 10.12 RESOLVED DUPLICATE 196511 https://bugs.webkit.org/show_bug.cgi?id=170874 https://bugs.webkit.org/show_bug.cgi?id=196511 P2 Normal --- 1 chudesno webkit-unassigned aestes ap pvollan timothy wenson_hsieh oldest_to_newest 1384078 0 chudesno 2017-12-21 03:06:36 -0800 Steps to reproduce: 1. Open any webpage in Safari 2. Select a few files in Finder and drag them onto the page. Mind the files count shown in a red circle next to the cursor in osX. Expected result: Files count shows the number of files being dragged https://i.stack.imgur.com/lNXFu.png Actual result: Files count resets to 0 once over web page opened in Safari. https://i.stack.imgur.com/f0bRL.png Screenshots and the problem title are taken from Stackoverflow question. https://stackoverflow.com/questions/27797760/dropping-multiple-files-to-safari-changes-the-file-counter-to-0 1384314 1 ap 2017-12-21 16:51:48 -0800 Could you please confirm which Safari (Tech Preview?) version you are seeing this with? 1384430 2 chudesno 2017-12-22 01:27:25 -0800 That happens with Version 11.0.2 (12604.4.7.1.4) and Tech Preview Release 46 (Safari 11.1, WebKit 12605.1.18.2). Also, just mentioned that it is not 100% consistent. If I drag over rapidly, it may show the correct files number. But if I cross the Safari window border slowly it always resets to 0. 1384432 3 chudesno 2017-12-22 01:30:21 -0800 Also, I was able to find a post on stackoverflow dated Jan 2015 about this issue. https://stackoverflow.com/questions/27797760/dropping-multiple-files-to-safari-changes-the-file-counter-to-0 So it seems to be there for a while now. Thanks for having a look into this! 1386965 4 ap 2018-01-08 15:46:38 -0800 See also: rdar://problem/34373187 (didn't read it carefully enough to be sure if that's the same issue). 1523809 5 timothy 2019-04-03 11:32:01 -0700 *** This bug has been marked as a duplicate of bug 196511 ***