321660 - Margins on Page Setup always truncated down to nearest tenth

Status: RESOLVED DUPLICATE of bug 240896

(Firefox :: General, defect)

Description

[John Van Essen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

I want to print the approximately 5th page of a web page, but the info is split across printed page boundaries.  So I tried to fine-tune the bottom margin value to line up the area of interest on a single printed page, but the resulting value is always truncated down to the nearest tenth.

For example, entering 0.95 (which is about what I need) ends up being 0.9.

Please loosen this restriction - truncate down to nearest hundredth.


Reproducible: Always

Steps to Reproduce:
1. File -> Page Setup -> Margins
2. Enter 0.95 for bottom margin
3. Exit setup and re-enter - margin is 0.9

Actual Results:  
Margin value of 0.9

Expected Results:  
Margin value of 0.95

Comment 1

[Jacob Floyd]

I can confirm that this bug exists in the following on Linux 2.6.15 (2.6.15-gentoo-r1)

FF 1.5.0.1
Mozilla 1.7.12
TB 1.5 (20051201)

In all of the above, saving .25 as a value for margin in the Print Dialog, followed by reopening the dialog to verify the values, all digits beyond the tenths place are truncated.

However, about:config (in all apps) reports the correct value, the value with hundredths place digit.

This appears to be a case of UI truncation. The correct value is in fact saved.

Note that the UI truncates, it does not round. e.g: ".23", ".24", ".25", and ".26" all show up as ".2" in the Page Setup Dialog.

I think a clearer summary is:
Margins are truncated (no rounding) to tenths place in Page Setup Dialog, but saved correctly in about:config

Someone with enough power needs to change the following for this bug:
Product: Core
Componenent: Printing
Kewords: uiwanted
OS: All
Assignee: [e-mail]
Status: New

Comment 2

[Gérard Talbot]

*** This bug has been marked as a duplicate of 240896 ***