Recommended Posts

I use my computer on a 61 LED DLP

I use vista DPI scaling to make sure everything is nice and readable the buttons and menus are large. its set to 150% or 144pixels

Since Firefox 3 has been alpha it was the best web browser for me based that it had DPI scaling. The buttons, menus, web pages are all perfectly fit (DPI scaled and enlarged )then second I installed it no configuration. Every build.

Until RC1

My buttons, menus are microdots and so is the web. I can use its zoom feature to make the web biggers but my buttons are on default large and cant make them bigger. they killed the feature where it would look at your DPI windows scale and auto set the browser.

I cant even manually do it as for as I know...

Please help me get this back with maybe some hidden features or configuration. I know firefox has the configuration page but have no idea what to change or if its even there...

I will go crazy if this feature is no more available I will go back to beta 5 if I have too. My res is 1920 x 1080 and I sit about 5-8 feet back

1. I would love some help from you firefox nuts

2. A link where I can complain to Mozilla where it could actually be read

**EDIT**

Put up screen shot everything I circled in red is small. If you look at the start menu for vista it has nice clear text and icons, firefox3 (not 2) had the same enhancement with no configuration period. not look at the size of the text difference and the icons for the my favorites onthe top and the navigation buttons eveything is small

8 feet back this make things unreadable...

Im going crazy already please help

post-109068-1211066927_thumb.jpg

Edited by 1Way Jonny
I have no idea how to fix your problem but can I see a picture of that 61 LED DLP? :p

sure

horrible iphone pictures

It has 7.1 fiber optic Dolby Digtal to a Yamaha Reciever w/ a Bose Sound System

Quad Core

Stiker Extreme

4GB OCZ Reaper Mem

post-109068-1211067282_thumb.jpg

post-109068-1211067302_thumb.jpg

browser. display. screen_resolution Integer Firefox 1.5 only DPI of display device. Affects CSS absolute length units (e.g. pt, mm).

-1 (default): Use the operating system's logical resolution or 96 DPI, whichever is greater

0: Force use of operating system's logical resolution

(N): Assume screen DPI of n. Default DPI is 96.

Note: In Firefox, this can be changed via "Tools → Options → Content → Advanced → Display Resolution". See browser. screen_resolution for Firefox 1.0.x or layout. css. dpi for Firefox 2.0+.

just found some info on this

man this really blows

the option is there but not in firefox 3

installed firefox beta5 back, everything was small before, firefox 3 gave me hope the jacked it

just to show how dramatic it is i put up another screen look at the menus, button on top of my favorites sites, option menus and the navigation buttons

post-109068-1211068907_thumb.jpg

yes this is the option i need

layout.css.dpi

but its not in the about:config does anybody knnow how to edit this this is what I need NOT a ZOOM feature

Caveats

* This preference is not meant as a general ?zoom? feature to scale all rendered web content.

* This preference has no effect in Windows (the OS?s DPI setting is queried directly).

mmm let me get this straight

firefox completely disregards the OSs DPI settings? before rc1 you could see the text in the correct size without doing a zoom? I have tried rc1 on ubuntu and apparently firefox overrides the font hinting/antialiasing configuration and it looks like crap. so to me it sounds like something's broken now that wasn't broken before

As for the icons, I'm not sure DPI should affect the icons on the firefox toolbar, unless the icons are set to resize themselves inside the toolbar in case the text size increases.

Anyway, I would report a bug or check the mozilla zine forums in case more people are reporting problems like this.

I would suggest you to revert back to beta 5.

mmm let me get this straight

firefox completely disregards the OSs DPI settings? before rc1 you could see the text in the correct size without doing a zoom? I have tried rc1 on ubuntu and apparently firefox overrides the font hinting/antialiasing configuration and it looks like crap. so to me it sounds like something's broken now that wasn't broken before

As for the icons, I'm not sure DPI should affect the icons on the firefox toolbar, unless the icons are set to resize themselves inside the toolbar in case the text size increases.

Anyway, I would report a bug or check the mozilla zine forums in case more people are reporting problems like this.

I would suggest you to revert back to beta 5.

yes the DPI ONLY got scaled in firefox 3 the buttons menus everything, look at the first screen shot of the start menu text size and the browser, then look at the text between the two again on the second screen shot where i installed beta 5 back. Its a huge difference and it went into the menus, the address bar.

Even look the the back and foward buttons, the tabs firefox 3 rescaled every part of the UI its a great feature.

This was not the zoom feature, i didnt even have the zoom "ON" that beta 5 screen shot is the default option & look

If you guys have beta in vista 5 in vista (not sure about XP) change your DPI if you have a high res and watch the firefox match what you change it too

**EDIT**

i believe this is the correct thing to edit "Layout.css.dpi" its not the about:config in Firefox 3 beta 5 or RC1, the description of what "Layout.css.dpi" does is right on the money but missing, how else to edit this?

Edited by 1Way Jonny
Have you tried a different theme? Classic Compact 3.07 is compatible with RC1.

thanks but i just want the default theme, this has nothing to do with the theme or anything but the information you found about scaling

"Layout.css.dpi"

someone else reporting the same thing on mozilla zine, I believe

http://forums.mozillazine.org/viewtopic.php?t=656301

apparently an extension might solve your problems

dont need the extension because that feature for global min ZOOM is in firefox, after he installed he still had the same problem with the GUI being small and not scaled. looking to get the web and the GUI scaled with no plugins

chrome has the ability to do it its just has a name change for the option in about:config

can someone with an account there post this link so he can see the issue here...

Hmm, if this regressed in RC1, it really do sound like a bug should be filed at it on Bugzilla. :-/

I filed something on mozilla website can you give a link to where i should def submit to?

There is this extension that isa compatible that will allow you to edit CSS.

https://addons.mozilla.org/en-US/firefox/addon/179

thanks ill try it now

Guys your support has been great we all know now what the problem is and this feature of CSS/Chrome just need to fix it

You can file a bug report here https://www.mozdev.org/bugs/enter_bug.cgi You will have to register and login. It shouldn't take long.

Ok i registered and hit Submit bug when i get in and it gives a list of thousand of things to enter a bug about but no "Firefox"

this look like bug reports for addons, its says must pick a product to submit to

If that option doesn't exist in about:config, just create it (right-click -> New -> Integer).

http://kb.mozillazine.org/Layout.css.dpi

ok got good and bad news

you can add this option to the about:config in beta5 and change from -1 or 1 or 0 and it effect's exactly what we are talking about make everything go big small big small

we have found it and it works...

so i install RC1 back and added "Layout.css.dpi" in the about:config and set -1 then 1 then 0, just like in beta5, and it did nothing they definitely broke this... back to beta 5

grrr at least i know how to change this manually now, they just broke the option in RC1 which explains why the default mode isn't working automatically it's because the manual mode is broke

You set the DPI in the value, your monitor isn't 1DPI it ignores that value.

Set it to 96, 192, etc. (-1 is a special value, makes it take it form the OS)

Although it does look like it's a bug, so if people can verify it (and when it regressed) it should get fixed.

Edit: ok, didn't know it also took 0 as a special number)

  • 11 months later...
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!