Recommended Posts

I played a little with the new settings in the about:config that are introduced by this fix and the font looks much better now.The default values were not good for me.And they say this is only one of the issues causing the bad fonts so there may be more font fixes soon.

I played a little with the new settings in the about:config that are introduced by this fix and the font looks much better now.The default values were not good for me.And they say this is only one of the issues causing the bad fonts so there may be more font fixes soon.

Please share you settings with us, so we can also try..

Please share you settings with us, so we can also try..

Bug 642589 landed in today's nightly, so for everyone having trouble with font rendering, please have a look at the gfx.font_rendering.cleartype_params.* settings in about:config. The params follow the ranges given here: ClearType Registry Settings. In addition, the available rendering modes are explained here: DWRITE_RENDERING_MODE Enumeration. The numbers gfx.font_rendering.cleartype_params.rendering_mode takes correspond with these modes as follows: "0 = default, 1 = aliased, 2 = GDI Classic, 3 = GDI Natural,

4 = Natural, 5 = Natural Symmetric]

Source: mozillazine forum

LOL.I didn't play with the gfx.font_rendering.cleartype_params.rendering_mode,just with the contrast,gamma and cleartype lvl ones.But when i set those to default and gfx.font_rendering.cleartype_params.rendering_mode to "2" for GDI Classic it is now perfect!!!Like with the AA addon,but without the bad spacing.They finally fixed it!!!

Using the latest nightly from today, anyone else notice that Stylish doesn't open in it's own manage window now or is it just me? It forces it open in a tab so I can't search through my styles.

I can right click on the extension and get it that way.. but then it won't let me switch back to firefox without closing that window. :wacko:

Stylish 1.1.2

-Updated the toolbar button to act more like other toolbar buttons

-New default in Firefox 4 is to use the Add-ons Manager when choosing Manage Styles. The setting extensions.stylish.manageView is still available - 0 for add-ons manager, 1 for stand-alone dialog, 2 for sidebar

-Added links for creating a new style and going to userstyles.org in add-ons manager

-Removed Page Style overlay

-Fixes for latest Firefox, Seamonkey, and Thunderbird

-Updated Czech and Japanese localizations

-Added partial Romanian localization

Edit:

Also, you can edit your styles through the addons manager, BUT NOT on the EXTENSIONS tab, but on the USER STYLES tab.

Thanks, it's odd though because Firefox 4 has the normal behavior I'm used to, while the nightly doesn't. Not a big deal though.

in about config, set:

extensions.stylish.manageView

to 1 to make it open in a dialog!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      262
    3. 3
      Skyfrog
      86
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!