Browser compatibility update for Pegasus (main)


Recommended Posts

uhhh never had any problems with themes or any of the settings in any browser I tried (IE8/9,Firefox stable/nightly,chrome,and even opera) so who was complaining???

and the default theme is too bright!!! ouch! I want my darkside to stay.....

also segoeui sucks. it's very hard to read. I have candara for all my windows fonts even and it's so much easier to read. the numbers especially.

I also use a dark windows theme and dark chrome theme.

I've been a supporter of Pegasus since its incarnation, but add me to the list of those upset at the removal of darkside... Hopefully I misunderstood the OP and it will actually make a return soon. And for god's sake please don't tell me the forum themes will be removed when this "upgrade" makes its way there.

P.S. I'd take blurry "welcome" text and darkside over clear "welcome" text and default Pegasus theme any day.

Just like the 1 or 2% of users that complained about the tab animations in firefox and it went away, it made it take up more P/F delta, was harder to move tabs around, and locked up other things on my computer. (just becuase it used 2-3% more CPU and broke obscure add-ons)

OCCUPY NEOWIN!!!!!!!!!!!!!!!

Thanks for making the news a section I won't visit anymore. White background? your kidding. I had no problem with the themes on IE/Chrome or Firefox.

Bring back the themes, I Miss the dark look :(

Thanks for making the news a section I won't visit anymore. White background? your kidding. I had no problem with the themes on IE/Chrome or Firefox.

Bring back the themes, I Miss the dark look :(

Are you serious? Almost every website's content is on a white background.

No more font-settings? I have OSX Lion with Safari, and Segoe font looks bad and blurry (only on neowin) :/ Please bring back at least one more font (for example: arial or tahoma). :rolleyes:

Fixed by installing "Segoe UI" fonts from Windows 7 into OSX. Now the fonts are all good.

(I only had "light" version of segoe font in Lion, I think that was the problem.)

Looks like crap, far too bright for those of us with eye problems it literally glares now! Dark is better, for me at least. This coupled with the forum issues Im having it's adios Neowin ...

I do not like the darker background on the front page at all. Pegasus with the lighter background was my favourite (Y)

Agreed. I liked the light grey bars on the background ... I don't know why they were all changed to dark versions of blue?

Looks like crap, far too bright for those of us with eye problems it literally glares now! Dark is better, for me at least. This coupled with the forum issues Im having it's adios Neowin ...

^ What he said

Fact is, that with the lovely options we had we were driving people away due to browsers crashing on Neowin. Now it could be down to add-ons and betas and alpha builds, but we need a site that works all the time, on all browsers.

I can confirm that all my problems with Neowin on Google Chrome stable which were menus not displaying, bad fonts and choppy scrolling have now been fixed on the Main page with this update, just waiting for the Forums to be updated now as all those problems still persist on 'this computer' in the Forums. (Y)

Are you serious? Almost every website's content is on a white background.

Exactly what I was thinking lol. If you can't handle a site with a white/light bg good luck using the internet...

I understand that some people prefer dark themes, but the people posting that its "blinding" them are being extremely hyperbolic.

Exactly what I was thinking lol. If you can't handle a site with a white/light bg good luck using the internet...

I understand that some people prefer dark themes, but the people posting that its "blinding" them are being extremely hyperbolic.

There are those that are sensitive to bright lights,

Using this in Stylish for now until there's an option to bring back font choices:

html { font: 62.5%/1 Arial, FreeSans, sans-serif !important; }

Titles don't look right but I forget what they were before. :p

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

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!