about:support "ClearType Parameters" duplicates

RESOLVED FIXED in Firefox 67

Status

()

defect
P5
trivial
RESOLVED FIXED
3 years ago
Last month

People

(Reporter: alice0775, Assigned: emk)

Tracking

(Blocks 1 bug)

48 Branch
mozilla67
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox48 wontfix, firefox67 fixed)

Details

Attachments

(2 attachments)

Posted image screenshot
STR
1. Open about:support

Actual Results:
"ClearType Parameters" duplicates
See attached screenshot
Blocks: 1263849
No longer blocks: 1265711
Assignee: nobody → dvander
Status: NEW → ASSIGNED

I don't get any "ClearType Parameters" on Mac, so this could be windows-only. Does it still get duplicated? I notice there was some cleanup done at some stage (not sure if it was before or after this filed).

Assignee: dvander → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(alice0775)
Product: Firefox → Toolkit

I can still reproduce the issue on Nightly66.0a1.

Build ID 20190108101613
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Flags: needinfo?(alice0775)
Priority: -- → P5
Duplicate of this bug: 1530101

I guess David forgot to remove the explicitly added "ClearType Parameters" section when he re-added showing implicit data properties in his v3 patch in bug 1263849. Unfortunately both David and Milan are inactive now.

We should not add this section explicitly because it will also be added
implicitly and make a duplicate.

Depends on D21821

Attachment #9047912 - Attachment description: Bug 1265903 - Remove duplacated "ClearType Parameters" section. r?standard8 → Bug 1265903 - Remove duplicated "ClearType Parameters" section. r?standard8
Assignee: nobody → VYV03354
Status: NEW → ASSIGNED
Pushed by VYV03354@nifty.ne.jp:
https://hg.mozilla.org/integration/autoland/rev/469b9a046972
Remove duplicated "ClearType Parameters" section. r=Standard8
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
QA Whiteboard: [good first verify]
You need to log in before you can comment on or make changes to this bug.