HTML5 hole in major browsers... well, except for Firefox


Recommended Posts

The glorious future of the mighty Flash killer. Welcome, welcome. We've been expecting you. With all your ridiculously stupid troubles, too.

I know! Flash have never EVER have holes and security faults!

...

...

...

Shall I continue?

not trying to flame or anything, just my two cents....this serves to prove that nothing is flawless....instead of jumping the gun and trying to drop flash/flex and so on to adopt html5, one should wait until the platform matures enough and standards are set in stone.

^ Well, then perhaps we shouldn't have moved into this house yet... and set the old rented apartment ablaze with such a profound sensation of accomplishment? Gosh knows it may start to rain fish and the roof may not hold as well.

  • Like 3

one should wait until the platform matures enough and standards are set in stone.

If the effected vendors had actually paid attention to the spec that specifically has recommendations to stop this from occuring, naturally this wouldn't of happened.

Props to Mozilla for actually paying attention.

Mmm, yes.

Please, tell me more about how everyone should use Webkit instead of following open web standards. :whistle:

Given that the problem affects Trident and Presto as well that's a pretty stupid comment to make.

Given that the problem affects Trident and Presto as well that's a pretty stupid comment to make.

No, you just think it's stupid because you're a "Google shill", to borrow your own terminology from other threads.

This not only proves that open web standards and adherence to them is important, but that having a single rendering/layout engine is a bad thing.

So explain to me how it's Google's fault when Webkit (which Google do not actually make just FYI) is not the only browsing engine that is subject to the flaw?

So explain to me how it's Google's fault when Webkit (which Google do not actually make just FYI) is not the only browsing engine that is subject to the flaw?

You need to read the OP and maybe find an email for Feross Aboukhadijeh, he is the one that discovered it.

So explain to me how it's Google's fault when Webkit (which Google do not actually make just FYI) is not the only browsing engine that is subject to the flaw?

Oh, so Webkit isn't the holy grail of openness that you made it out to be in the Opera thread after all? Or is it just because this doesn't work in Google's favour?

They ship Webkit in both binary and source form, they contribute to the Webkit project, and they were supposed to be the so-called "champions of the open web". So yes, they're just as much at fault for shipping a broken, non-standard implementation as Opera and MSFT.

Funny how people twist your words here when you aren't prepared to sell your soul to Microsoft isn't it.

Chrome is open (ish, chromium), webkit is open. Never did I claim that software being open excludes it from carrying bugs or design faults. And given the other browsing engines it effects, it's clearly something that's common practice in the industry.

Funny how people twist your words here when you aren't prepared to sell your soul to Microsoft isn't it.

Chrome is open, webkit is open. Never did I claim that software being open excludes it from carrying bugs or design faults. And given the other browsing engines it effects, it's clearly something that's common practice in the industry.

Because supporting open web standards means you're a Microsoft supporter, amirite? (Mozilla would of been far more apt)

You argued in favour of Webkit dominance, and now you don't even have the integrity to stick to your own words. Pathetic.

Another misconception. I still think it would be good if they all worked towards the same goal instead of having to compete with each other, I also accept that no software, proprietary or open source is completely free from flaws. If you want to warble on about integrity how about putting your money where your mouth is and not twisting my words? ;)

Another misconception. I still think it would be good if they all worked towards the same goal instead of having to compete with each other, I also accept that no software, proprietary or open source is completely free from flaws. If you want to warble on about integrity how about putting your money where your mouth is and not twisting my words? ;)

"Flaws"

You mean ignoring the large, red-backgrounded section of the localStorage spec that specifically warns about this "flaw"? Hah!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. About time.
    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
    • Windows 11 gets new audio improvements in the latest builds by Taras Buria Today's Experimental builds (26H1 and Future Platforms, formerly Canary) pack several audio-related improvements. If your device is enrolled in the Experimental Channel (26H1), you can download build 28120.2315, while those in the Future Platforms version have build 29613.1000 to try. Here is what is new in build 29613.1000: [Audio] Following up on our previous improvements, we’re making some more adjustments to Settings > System > Sounds based on your feedback. Namely, we’ve updated the “All sound devices” page so: You now have the ability to change default devices from this page. Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. We’ve adjusted the page design slightly so now you can filter whether you’re viewing input or output devices. We’ve added toggles so you can choose if you want to hide or show disabled, disconnected, and unplugged devices on this page. We’ve also updated the input and output audio properties page for devices in Settings to now include jack information for those that need it. And here is the changelog for build 28120.2315: This update includes a small number of minor bug fixes and improvements. [Accessibility] This update improves caption style responsiveness by redrawing captions immediately for caption style changes. If no current caption is visible, a sample caption string is displayed. [Audio] This update improves the reliability of the inbox HD Audio driver. You can find the official release notes for build 28120.2315 here and for build 29613.1000 here.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      576
    2. 2
      +Edouard
      189
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      78
    5. 5
      neufuse
      72
  • Tell a friend

    Love Neowin? Tell a friend!