Bug In Samsung S3 Grabs Too Many Images, Ups Data Use 99
First time accepted submitter Emmanuel Cecchet writes "Researchers of the BenchLab project at UMass Amherst have discovered a bug in the browser of the Samsung S3. If you browse a Web page that has multiple versions of the same image (for mobile, tablet, desktop, etc...) like most Wikipedia pages for example, instead of downloading one image at the right resolution, the phone will download all versions of it. A page that should be less than 100K becomes multiple MB! It looks like a bug in the implementation of the srcset HTML tag, but all the details are in the paper to be presented at the IWQoS conference next week. So far Samsung didn't acknowledge the problem though it seems to affect all S3 phones. You'd better have an unlimited data plan if you browse Wikipedia on an S3!"
If this was really a problem... (Score:3, Insightful)
Company reactions to major problems. (Score:2, Insightful)
Except is an *Overstated* Bug (Score:4, Insightful)
If this was really a problem it would have been noticed a long time ago.
The summery overstates what is going on, it implies that using a surfing on a S3 Phone will cause you to burn several times the magnitude of bandwidth it should, its subterfuge.
Its simply a bug in the stock web browser that does not break page views. that systematically downloads all images in a srcset instead of picking only the one it needs. An example "" if its not used...it does not happen.
Why is it not being discovered is that it does not make enough of an impact in common usage. I suspect additionally if your have a carrier like mine they simply serve a compressed version of the original image anyway, or S3 users are now using like me Chrome. Popular alternatives like the offer the same functionality.
The bottom line is Browser have bugs. That is not news, this is neither a critical, or even as stated a bandwidth hog.
Nothing to do with Linux (Score:3, Insightful)
That's right! This is Linux. Not that Apples or Microsoft shit. Nothing ever goes wrong in Linuxland. Any kind of "error" you have with Linux is because you're too inept to use a computing device. Any real user would have rooted this phone and installed CustomModXYZ 10.43222.8a.
...Ironically This is nothing to do with Linux(The Kernel) this is a *bug* in the stock browser, you can ignore it and simply use Opera or Chrome on Android, Would the same true for Apples or Windows Shit(sic).