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

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!