Closed Bug 869890 Opened 8 years ago Closed 8 years ago

thunderbird should declare itself dpiAware on windows via the .exe manifest

Categories

(Thunderbird :: OS Integration, defect)

22 Branch
x86
Windows 7
defect
Not set
normal

Tracking

(thunderbird22 fixed)

RESOLVED FIXED
Thunderbird 23.0
Tracking Status
thunderbird22 --- fixed

People

(Reporter: jfkthame, Assigned: jfkthame)

References

Details

Attachments

(1 file)

In bug 866365, we removed the call to SetProcessDPIAware from XRE_mainInit(), and instead added the dpiAware element to firefox.exe's manifest. (This is the MS recommended way for an application to declare itself dpi-aware, as per MSDN documentation.)

So to maintain its existing behavior on hi-dpi windows systems, thunderbird should make the same manifest addition. Bug 866365 is likely to be uplifted to mozilla-22, I think, so that's also where the manifest change should be made.
Depends on: 866365
Assignee: nobody → jfkthame
Comment on attachment 746893 [details] [diff] [review]
declare thunderbird.exe as dpi-aware in its manifest

Not tested, but looks fine as a copy of what was landed for FF. r=Standard8.
Attachment #746893 - Flags: review?(mbanner) → review+
https://hg.mozilla.org/comm-central/rev/f85134b411f6
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 23.0
Comment on attachment 746893 [details] [diff] [review]
declare thunderbird.exe as dpi-aware in its manifest

[Approval Request Comment]

See bug 866365 comment 46. The change there has just landed on Aurora, so the matching thunderbird change also needs to be uplifted.
Attachment #746893 - Flags: approval-mozilla-aurora?
Attachment #746893 - Flags: approval-mozilla-aurora? → approval-comm-aurora?
Comment on attachment 746893 [details] [diff] [review]
declare thunderbird.exe as dpi-aware in its manifest

[Triage Comment]
The core patch is on beta now, post merges, so we'll take this on beta as well.
Attachment #746893 - Flags: approval-comm-aurora? → approval-comm-beta+
You need to log in before you can comment on or make changes to this bug.