Recommended Posts

This page hasn't yet (at the time of posting) been updated:

https://www.mozilla.com/en-US/firefox/channel/

coz may 17 was just aurora to beta merge day , not public release day , read meeting notes

Please note that this is not the date users will see an update available

Anyone else seeing this problem?

Nope, everything works fine in here, try to run Firefox in safe mode with disabled all extensions, maybe one of them cost You a problem, also did You use some scripts to change addon manager layout etc?

But I'm facing other problem with Aurora and Nightly, I can't drag window with mouse, Aero snap and shake duno work any more, can someone confirm or I must look for problem in my Sys. settings?

EDIT: TMP was a problem.... solved

Are they ever giong to fix the font rendering in Firefox?

Looks just terrible compared to Chrome/IE/Opera

It looks fine to me personally. That being said, the 6.0 nightly builds - soon to be on the Aurora channel - offer more fine-grained control over the font rendering. See this mozillaZine forum post for more details.

Firefox 6.0 and higher with 'gfx.font_rendering.cleartype_params.rendering_mode' set to '2' in about:config is probably what you're looking for.

Are they ever giong to fix the font rendering in Firefox?

Looks just terrible compared to Chrome/IE/Opera

Firefox uses the same font rendering APIs as Firefox, Chrome and Opera just haven't caught up yet.

When is Mozilla going to implement a native pdf viewer in Firefox?

Probably never, no other browser does it (Chrome just bundles Acrobat)

Firefox uses the same font rendering APIs as Firefox, Chrome and Opera just haven't caught up yet.

Probably never, no other browser does it (Chrome just bundles Acrobat)

Hm? I was under the impression that Google rolled their own PDF viewer for Chrome rather than bundling Adobe Reader components.

Edit: They are rolling their own:

pdfdllchrome.png

Found in C:\Users\<user name>\AppData\Local\Google\Chrome\Application\<version number>\

I was originally planning to switch to beta/aurora eventually, but I haven't been haven't had a single problem with the nightly channel so far.

Yup... Luckily is so stable it's like getting only fixes/improvements...

I use 6?1 as default... Even the x64 build.

Same happens with ABP preview builds ( 1.38? currently ).

We're lucky I suppose.

But also it's expected in a way, 'cause the rapid release cycle, makes only few changes, like Chrome and not many major ones which are most likely to give problems.

Firefox uses the same font rendering APIs as Firefox, Chrome and Opera just haven't caught up yet.

Probably never, no other browser does it (Chrome just bundles Acrobat)

Only if you use the default windows themes. Otherwise the font rendering is bad even with HW Acceleration off. You could use any visual style with Firefox3 and the font would look normal like other browsers.

This is fixed in firefox6. In firefox 6 there are settings in about:config to make directwrite render very similarly to classic cleartype.

It is half a shame this is what has come of directwrite. It looks quite a bit better for me, but I know many have had horrible issues with it. This will certainly prevent the adoption. I wonder why it looks horrible for some and great for others? The variability in the monitors that are used?

OS X has a smoother font rendering as well. Not as sharp, but still clearly defined.

Hm? I was under the impression that Google rolled their own PDF viewer for Chrome rather than bundling Adobe Reader components.

Edit: They are rolling their own:

pdfdllchrome.png

Found in C:\Users\<user name>\AppData\Local\Google\Chrome\Application\<version number>\

Hmm, last time I tried it, it just loaded Acrobat (I knew it was separate since the system only had Acrobat 9, but Chrome was showing Acrobat 10 widgets)

Only if you use the default windows themes. Otherwise the font rendering is bad even with HW Acceleration off. You could use any visual style with Firefox3 and the font would look normal like other browsers.

Font rendering is the same regardless of the Windows theme.

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

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • 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.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • 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
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!