Closed Bug 151779 Opened 23 years ago Closed 23 years ago

line-height css property in body attribute style incorrectly stored

Categories

(Core :: DOM: Editor, defect)

Product:
Core
Component:
DOM: Editor
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: fredrik.wendt, Assigned: kinmoz)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020412 Debian/1.2.0-6 BuildID: 2002061004 Whenever line-height is entered as "1.4" it gets translated into 1,4 (comma as decimal delimiter) which is incorrect, with the effect that it must be reentered. Reproducible: Always Steps to Reproduce: 1. Compose a new HTML mail. 2. Move cursor into text area, select Format -> Page Colors and Background. 3. Click Advanced Edit, choose tab Inline Style. 4. Enter property "line-height" and value "1.4" 5. Click OK 6. Click Advanced Edit (yes, again) 7. Note that the value is now changed. 8. Click OK 9. Click Advanced Edit (yes, for the third time) 10. Note that the value is now gone. (My guess: since the assembled body tag attribute style's value string no longer can be correctly interpreted.) Actual Results: The line-height value is converted to use of a decimal delimiter of , (comma) instead of . (period), which violates the specification, and breaks proper use of the property. Expected Results: The value should be converted (if needed) the other way round.
This also happens when "font" property is entered as for example "12pt/1.4 sans-serif", as run here: http://lxr.mozilla.org/mozilla1.0/source/content/html/style/src/nsCSSParser.cpp#4847 I checked whether this was mailnews specific or not. It wasn't, the same thing happens in the page composer. BuildID: 2002061321
I figure this bug should be moved to Product-Browser, Component-Editor:Core. Trying to do this.
Component: Composition → Editor: Core
Product: MailNews → Browser
Target Milestone: --- → M1
Added Kin as cc (should've been informed of this bug from the beginning (my guess)).
Target Milestone: M1 → ---
reporter (Fredrik Wendt): can you reproduce this bug with a recent build of mozilla (for example, 1.1beta)? if so, please comment again with details. if not, please resolve this bug as WORKSFORME. thanks.
Assignee: ducarroz → kin
QA Contact: esther → sujay
this worksforme on my mac debug trunk build from 2 days ago
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.