Recommended Posts

I am using IE10 from Windows 8 RTM. I cannot press enter and go to next line. This does not work while creating or modifying a post. Anyone with this issue?

AFAIK it's a known issue here on neowin atm

I personally don't know if it's an IPB bug or just a neowin bug, if it's IPB related there's not much neowin can do till the next update

Yeah I get the thing where you can't press enter, just gotta turn off WYSIG mode (going back to plain text) then you can press enter so it might be a simple (temporary) fix for now at least.

It wasn't that way on RP or CP AFAIK.

Yeah I get the thing where you can't press enter, just gotta turn off WYSIG mode (going back to plain text) then you can press enter so it might be a simple (temporary) fix for now at least.

erm, how would I go about doing that?

I am using IE10 from Windows 8 RTM. I cannot press enter and go to next line. This does not work while creating or modifying a post. Anyone with this issue?

Not just on IE10, happens in Chrome sometimes as well. Although pressing shift + enter works in Chrome whereas it doesn't in IE10

erm, how would I go about doing that?

When you start typing here in the quick reply window, there's a little switch on the top left of the box. Click that to turn it off and you can always turn it back on without losing anything typed.

I am using IE10 from Windows 8 RTM. I cannot press enter and go to next line. This does not work while creating or modifying a post. Anyone with this issue?

I was JUST about to post about this. Been going on for weeks, and driving me NUTS!

When you start typing here in the quick reply window, there's a little switch on the top left of the box. Click that to turn it off and you can always turn it back on without losing anything typed.

oh cool, thanks :D

I was JUST about to post about this. Been going on for weeks, and driving me NUTS!

LOL, me too :p

I am using IE10 from Windows 8 RTM. I cannot press enter and go to next line. This does not work while creating or modifying a post. Anyone with this issue?

I wasn?t having this problem until a few weeks ago. You can temporarily resolve the issue by forcing IE into in a specific compatibility mode. For me the issue happens because the browser is defaulting to IE9 mode with IE10 standards.

1. Press F12 to enter Developer Mode.

2. Set Menu "Browser Mode" to "Internet Explorer 9"

3. Set Menu "Document Mode" to "Internet Explorer 9 standards"

Otherwise set both "Browser Mode" and "Document Mode" to "Internet Explorer 10" values, however the full editor will act a bit buggy when fully in IE10 render mode.

Long term, the issue can be resolved by neowin forcing IE10 into a specific render mode, or eventually Microsoft may add it to a compatibility mode update. (http://msdn.microsof...y/cc288325.aspx) Its also possible that the compatibility update for IE10 already exists, but only for RTM.

  • Like 2
This bites. they only offer IE10 for windows 8? am i to understand that Win8 won't allow for other browsers? Sorry I'm not up on the latest but is this true?

If you're joking: LOL :D

If you're serious: erm, no, Chrome, Firefox, Opera, Rockmelt, IE, and every other browser that worked in Win 7 is still supported in Win 8 :D

This bites. they only offer IE10 for windows 8? am i to understand that Win8 won't allow for other browsers? Sorry I'm not up on the latest but is this true?

No. IE10 will be released for Windows 7, and other browsers won't be allowed to access low level system API's in the RT version of Windows, they will only be allowed into the Windows 8 store if they run as fully RT code which means IE will have a significant advantage on the ARM version of Windows 8.

This bites. they only offer IE10 for windows 8? am i to understand that Win8 won't allow for other browsers? Sorry I'm not up on the latest but is this true?

windows 8 can still run any browser. only on ARM machines will you be restricted to IE (unless MS eventually decides to allow other browsers in the market)

No. IE10 will be released for Windows 7, and other browsers won't be allowed to access low level system API's in the RT version of Windows, they will only be allowed into the Windows 8 store if they run as fully RT code which means IE will have a significant advantage on the ARM version of Windows 8.

I appreciate that. If it works good and I like it, I'll definitely use it as my primary browser. I'm just surprised they haven't released a "public release" aside from Win8 public preview. but thank you

No. IE10 will be released for Windows 7, and other browsers won't be allowed to access low level system API's in the RT version of Windows, they will only be allowed into the Windows 8 store if they run as fully RT code which means IE will have a significant advantage on the ARM version of Windows 8.

how much you wanna bet there will be a "Jailbreak" of sorts for Windows RT? :p

i personally wouldn't be surprised in the least

What has that got to do with this topic?

Anyway, cheers to whoever suggested the dev mode trick. I am forcing IE10 to run in IE9 mode and enter button now works to go to next line.

interesting.. I never knew that existed. did you have to add a /devmode to the command line or is that in the settings?

I appreciate that. If it works good and I like it, I'll definitely use it as my primary browser. I'm just surprised they haven't released a "public release" aside from Win8 public preview. but thank you

My guess is that IE10 will be released for 7 at the same time that Windows 8 reaches general release. The improvements aren't as big as from IE8 to IE9 so I wouldn't call it a must have but in UI terms not much has changed so there won't be much for you to adapt to, just a few under the hood improvements mainly :)

how much you wanna bet there will be a "Jailbreak" of sorts for Windows RT? :p

i personally wouldn't be surprised in the least

Oh I have no doubt people will try it, but unfortunately that will be of no value if the major browser vendors cease development on their browsers because of the restrictiveness of all of this.

Personally I have a feeling the antitrust folks may yet have something to say about it but yeah I'm sure people will try to hack them.

interesting.. I never knew that existed. did you have to add a /devmode to the command line or is that in the settings?

As I recall at one time it had to be enabled, but that was a very long time ago now I think. On at least IE9 and IE10 you just hit F12 or look under the Tools menu.

This is also what to use if you want to alter IE's user agent strings on the fly under the Developer Mode Tools menu.

Oh I have no doubt people will try it, but unfortunately that will be of no value if the major browser vendors cease development on their browsers because of the restrictiveness of all of this.

Personally I have a feeling the antitrust folks may yet have something to say about it but yeah I'm sure people will try to hack them.

I doubt they'll cease development, they'll probably even release versions to the market eventually, and it's when that happens that a "Jailbreak" of sorts will come in handy.

i expect a tweak to eventually release similar to this tweak that just released recently for iOS http://www.iphonehacks.com/2012/07/nitrous-enables-faster-nitro-javascript-engine-for-third-party-apps.html

I doubt they'll cease development, they'll probably even release versions to the market eventually, and it's when that happens that a "Jailbreak" of sorts will come in handy.

i expect a tweak to eventually release similar to this tweak that just released recently for iOS http://www.iphonehac...party-apps.html

I have a feeling that they will release neutered versions that comply with the RT guidelines just to get in the store. Which would mean there would be little advantage to a jailbreak. Of course that wouldn't stop developers trying to port the code themselves so you still have a good point

This topic is now closed to further replies.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!