files being uploaded are always represented to a destination site as huge-sized (Win64; 0.5.11)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Confirmed
|
Medium
|
Unassigned |
Bug Description
When I try to upload some tiny files to a post-office site, the post-office interface says that these files are NNNN GigaBytes long. So, most of such systems do not accept my files at all, some of them try to upload files to a file hosting. Technically, the upload process itself may work OK in some cases (at least, once I was lucky to upload 50 MBytes video to VK.com - because VK runs a very robust user interface, which usually works in all possible cases; nevertheless, even VK later failed to measure a size of that Midori-uploaded content)... But, as I alredy said, the uploading file size is reported totally wrong by Midori.
(I use: Midori 0.5.5 (En-UK), win7 (Ru, genuine); Intel x64 triple-core 3 GHz; 4 Gbyte RAM; ATI video.
Here is what Midori says about my desktop computer system in its about:version...
{
Version numbers in brackets show the version used at runtime.
Command line F:\Program Files 2 (x86)\Midori\
Midori 0.5.5 ((null))
GTK+ 3.6.2 (3.6.2) Glib 2.34.3 (2.34.3)
WebKitGTK+ 1.10.1 (1.10.1) libSoup 2.40.2
cairo 1.10.2 (1.10.2) libnotify No
gcr No granite No
single instance Sockets
Platform Windows NT 6.1
Identification Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.6 (KHTML, like Gecko) Chrome/
Video Formats H264 [x] Ogg Theora [x] WebM [x]
Netscape Plugins:
Google Update Google Update
Java Deployment Toolkit 7.0.400.43 NPRuntime Script Plug-in Library for Java(TM) Deploy
Windows Activation Technologies Windows Activation Technologies Plugin for Mozilla
Shockwave Flash Shockwave Flash 11.8 r800
Java(TM) Platform SE 7 U40 Next Generation Java Plug-in 10.40.2 for Mozilla browsers
Unity Player Unity Player 3.5.5f3
Silverlight Plug-In 5.1.20513.0
}
)
Changed in midori: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
summary: |
files being uploaded are always represented to a destination site as - huge-sized (Win64; 0.5.5) + huge-sized (Win64; 0.5.11) |
What's the status on this issue? Why has nobody resolved it? Why do you just leave behind bugs? Are you too lazy to fix them? Are they not worth fixing? Do you not care about the Windows version?