Recommended Posts

If you jump into the source of, say this page, it's quite a bit of a mess with regards to corners: there's the prefix for Webkit browsers, the prefix for Gecko, and the non prefix for Trident or Presto. For now some sites assume only the first two, not the latter.

With regards to the OS X complaints, I did have a quick look at it and it does feel a little awkward. It's not that bad though... if you want really awkward, check out the Linux port. :p

Opera is probably the only browser that actually fucntions properly on linux.

Chrome, the text and the adress bar is either to high or to low, and it jumps between the two for every letter I type.

Chrome and FF both ignore whatever icon theme Gnome is using. Chrome uses some of the OS cursors, FF just say "nah, I really don't like the OS cursors, you're going to use this special in FF only cursors because that's what I say"...

Opera is probably the only browser that actually fucntions properly on linux.

Chrome, the text and the adress bar is either to high or to low, and it jumps between the two for every letter I type.

Chrome and FF both ignore whatever icon theme Gnome is using. Chrome uses some of the OS cursors, FF just say "nah, I really don't like the OS cursors, you're going to use this special in FF only cursors because that's what I say"...

That's odd... the Opera port has different font rendering in the UI and webpages compared to the rest of the system. I'm basing this off running Opera in Ubuntu 10.04.

Imagine you have 30+ active tabs. :wacko: It's irritating for people who use Opera with lots of tabs always active (like I do), plus you can always activate it in Preferences

I know it can be turned on again, but like I said, the default Win7 behavior is to have them on. I'd prefer most Windows applications to follow system standards whenever possible.

That's odd... the Opera port has different font rendering in the UI and webpages compared to the rest of the system. I'm basing this off running Opera in Ubuntu 10.04.

I've yet to see a browser that renders nice fonts on linux though. but not as annoying as the cursor thing. Bur fonts on linux browsers tend to be a lot smaller than they should be for some reason.

But it is part of the reason why I rarely boot into ubuntu, that and the horrible flash performance and lack of a decent RDP client to connect to my media center.

Also is it me or is the beta more unstable than the alpha ? the alpha/daily builds worked great for me. the beta seems to crash occasionally, and relatively often when I click tabs, maybe when I switch tabs to fast or something, not sure.

I've yet to see a browser that renders nice fonts on linux though.

Both Firefox and Chrome render the fonts for me exactly as they're instructed to via the Font settings in Gnome. Be it slight, medium, full hinting, autohint, subpixel or not, it renders it exactly as the rest of the system, without any deviations. Opera doesn't.

Both Firefox and Chrome render the fonts for me exactly as they're instructed to via the Font settings in Gnome. Be it slight, medium, full hinting, autohint, subpixel or not, it renders it exactly as the rest of the system, without any deviations. Opera doesn't.

Perhaps, but Opera seems to render fonts closer to like the webdesigner wanted it to be, though, it still looks toos mall on all linux browsers.

Its rendering engine follows all W3C requirements and regulations, it's HTML5 capable, etc., etc. The 'problem' is it's not a wh*re like the rest - rendering all sorts of crap in half-compatibility modes. It's strict and it renders dirty code the way dirty code is supposed to be rendered.

Huh? What are you talking about?

Opera is probably more of a "######" than the rest because it isn't supported by most sites. So it needs to add even more compatibility workarounds in practice. It was designed from the ground up to handle "Street HTML", as they call it. Meaning that they go out of their way to be compatible with crappy code.

Which is also why most compatibility problems are because of browser sniffing.

Huh? What are you talking about?

Opera is probably more of a "######" than the rest because it isn't supported by most sites. So it needs to add even more compatibility workarounds in practice. It was designed from the ground up to handle "Street HTML", as they call it. Meaning that they go out of their way to be compatible with crappy code.

Which is also why most compatibility problems are because of browser sniffing.

I don't quite think you understand how this works.

back in the days, the web was like the wild west, there was no standards. And only one browser even supported, promoted and followed the W3C suggestions. guess which one.

Today there are standards, andfor the web to work as big as it's gotten. Web sites need to follow these standards, so the browsers knows how to render them.

Both Firefox and Chrome render the fonts for me exactly as they're instructed to via the Font settings in Gnome. Be it slight, medium, full hinting, autohint, subpixel or not, it renders it exactly as the rest of the system, without any deviations. Opera doesn't.

Yeah, that's what I meant.

Would be nice if they can get this fixed by final, but at this rate it's probably going into a 10.6x release (if at all).

I know it can be turned on again, but like I said, the default Win7 behavior is to have them on. I'd prefer most Windows applications to follow system standards whenever possible.

What's also weird is that since they disabled taskbar thumbnails by default, sometimes the taskbar thumbnails break. For instance, I get only two window previews in the taskbar when I have seven tabs.

I don't quite think you understand how this works.

back in the days, the web was like the wild west, there was no standards. And only one browser even supported, promoted and followed the W3C suggestions. guess which one.

You don't understand how this works. If Opera had followed the standards 100% and refused to render broken code, it wouldn't have worked anywhere. So they did build Opera from the ground up for compatibility while at the same time working to push open standards.

Why does every Opera thread turn into a degeneration of the same arguments over and over again? If you people don't like it, don't use it. Personally, I love Opera. I find it works with every site I encounter. I love it's features. I love it's speed. I love how I never encounter bugs (yes, some people claim they encounter obscure bugs, but I have no issues). It works for me. That's what matters. I don't see firefox or chrome threads degenerating constantly like the Opera ones do from the get-go.

  • Like 3

Why does every Opera thread turn into a degeneration of the same arguments over and over again? If you people don't like it, don't use it. Personally, I love Opera. I find it works with every site I encounter. I love it's features. I love it's speed. I love how I never encounter bugs (yes, some people claim they encounter obscure bugs, but I have no issues). It works for me. That's what matters. I don't see firefox or chrome threads degenerating constantly like the Opera ones do from the get-go.

+1

probably because because of smaller user community of opera, haters think that they waltz over to opera threads and trash and get away with it :/

I know it can be turned on again, but like I said, the default Win7 behavior is to have them on. I'd prefer most Windows applications to follow system standards whenever possible.

They had it that way after the feature was first implemented but a lot of people complained in their forums and blogs so it was changed. Can't please everyone.

Btw. the new build released today fixes a lot of small stuff. Imo it's the best build since a long time.

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

    • No registered users viewing this page.
  • Posts

    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
    • wow. that color finally comes to Surface Pro. was always a little jelly when a friend had the sandstone Surface Laptop. I wonder how different this dune is from the sandstone. I'll be getting the dune version. always thought black and platinum were a little boring. I'll still have access to my blue Surface Pro 11 as it'll be a hand-me-down.
    • Looks a very subjective aren't they!? I like its simple design. I love the way Apple designs their products with function over form, minimalization, and simplicity over cluttered complex designs. Many, not all, of their products follow this trend, and the device becomes a tool rather than dominating the space. I do not however like their OS. I have never bought a Apple product, and while I'd consider the Neo for my wife, I am hoping there are better alternatives out there when her failing MacBook Pro 2017 finally stops. Fischer-Price is famously plastic, garish, and poorly made. Basically you're describing the Window Laptops the Neo competes against! This is how product design should be, and what Apple have often followed in recent years: https://tenprinciples.design/
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!