Internet Explorer 9 Beta 9.0.8027.6000 Leaked

By R27
in Web Browser Discussion & Support

 Share

Recommended Posts

Grand Master

+Frank B. Subscriber²

Posted
  • Subscriber²
Posted

Regarding the UI: What you see is what you will get in the final I believe. Apart from a few small tweaks here and there the final UI will look like the beta UI.

Grand Master

Ci7

Posted
Posted

Are those UI based btw? I have to figure that we won't see any UI changes till RC. This is more of a internal or closed beta 2 from the looks of it. It's more core engine changes like updating it to use the bits from PP7 (which could be the last one as far as we know) than any top level UI work.

nah it is related to web-rendering

it break some pages even with *IE8 engine* mode

Grand Master

George P Global Moderator

Posted
  • Global Moderator
Posted

RC shouldn't have any UI changes, that's why it's called "Release Candidate" All of the changes are usually done in the betas. Surely coming from Beta 1 to RC1 you should definitely see some changes but this (beta "2") is where they happen first.

I don't think that's the case, sure what we get with the RC should be final unless there's a huge outcry from people then they'll change it since they listen more to feedback now. The thing is they did the original open beta and collect feedback, any changes due to that feedback we won't see TILL we get the RC. If they were to do a 2nd open beta then ya, I'd agree with you but they're not.

Grand Master

Roger H. Veteran

Posted
  • Veteran
Posted

I don't think that's the case, sure what we get with the RC should be final unless there's a huge outcry from people then they'll change it since they listen more to feedback now. The thing is they did the original open beta and collect feedback, any changes due to that feedback we won't see TILL we get the RC. If they were to do a 2nd open beta then ya, I'd agree with you but they're not.

Well since this beta has a UI you would think the UI team was collecting info since the first release and then incorporating it as it goes which is why it's still an internal beta (private group). This has tweaks and whatever changes they (UI team) have been working on otherwise why would they release another beta (to the private group). The IE platform team has been pumping out stuff for a while now (up to PP7 public builds) and i'm sure the UI team hasn't just been taking whatever they coded months ago and slap it on with PP7 and say test this. That makes no sense what's so ever!

They are still collecting info and still working on stuff however and surely they'll be going to make some more changes before the RC comes out. From the looks of things however i doubt there will be any major changes. Windows 7 was built and designed from the beta stages and no major additions were done even when RC came along. They have probably reached a feature freeze already since they did with Beta 1 of Windows 7/Vista. It's just all tweaking from now on.

Grand Master

George P Global Moderator

Posted
  • Global Moderator
Posted

Well, I dunno what to expect, I only want some minor things UI wise but overall I like what I see now. Guess we'll know sometime in Dec when people expect we'll see the RC.

Grand Master

Roger H. Veteran

Posted
  • Veteran
Posted

Piracy? Reading classified intel isn't piracy (say this was a FBI leak as we do all the time on WikiLeaks.org). This is more an issue of having access to get something that you normally shouldn't. The only person that broke any rules is the person that leaked it. Granted the EULA probably says that if i'm not authorized to install it then i shouldn't but at the sametime that's like telling a fat kid to not eat cake!

Mentor

the better twin

Posted
Posted

What would you call posting links to it then ? Not sharing ?

Well i did nothing of the sort but that is the age old piracy question isnt it? Does providing links to pirated content class as piracy ala pirate bay. I dont believe it is. (I'm sure the music and film industry disagree :p).

Ultimately i believe the blame should always lie with the person who uploaded it for distribution in the first place.

Collaborator

JonathanMarston

Posted
Posted

Well since this beta has a UI you would think the UI team was collecting info since the first release and then incorporating it as it goes which is why it's still an internal beta (private group). This has tweaks and whatever changes they (UI team) have been working on otherwise why would they release another beta (to the private group). The IE platform team has been pumping out stuff for a while now (up to PP7 public builds) and i'm sure the UI team hasn't just been taking whatever they coded months ago and slap it on with PP7 and say test this. That makes no sense what's so ever!

We don't really know what the purpose of this build was. It could have been built from a different branch than the one the UI team has been working in. Part of the new development process that Microsoft started with Windows 7 was not to merge changes into the main branch until they are complete, so it could just be that only the download speed indicator in the download manager was complete.

I'm not saying there will be big UI changes in the RC, but this leak is no evidence that there won't be, either.

Grand Master

DrCheese

Posted
Posted

Did you know that this is known as piracy?

Neowin has always had a much more liberal policy towards Microsoft leaks, considering leaks were neowins entire reason for existing when it was created. Besides these kind of leaks are usually timebombed to hell and back anyway, even if they aren't the jokes on the end user who uses them indefinitely

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine

      By LoneWolfSL · Posted

      Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By Primey_ · Posted

      The nerve of Google to sign this.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By s0nic69 · Posted

      I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By The Norwegian Drone Pilot · Posted

      It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more

      By David Uzondu · Posted

      JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.

  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later

  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!