Closed Bug 1231047 Opened 9 years ago Closed 8 years ago

NPWindow width/height values are half of expected values when using Content Scaling

Categories

(Core Graveyard :: Plug-ins, defect)

defect
Not set
normal

Tracking

(firefox45 affected)

RESOLVED DUPLICATE of bug 820831
Tracking Status
firefox45 --- affected

People

(Reporter: qdot, Assigned: qdot)

References

Details

When using the content scaling in bug 820831, width and height values in the NPWindow struct are reported as half of their expected values. This needs to be fixed before bug 820831 can land.
This bug is in windowed mode only. However, when in windowless mode, flash content is for some reason automatically scaled by a factor of 2.
Jim, any idea what might be going on here? This blocks bug 820831, which manifests on hiDPI systems (i.e. really tiny controls on Flash video players and the like).
Flags: needinfo?(jmathies)
Can I get STR here? I'm not sure what this bug is. FWIW I can reproduce the shrunk controls on my yoga running at 2x.
Flags: needinfo?(jmathies) → needinfo?(ryanvm)
The only STR I know are "Open a Flash video player, observe tiny controls." AirMo is an example. Kyle, maybe you can provide more context?
Flags: needinfo?(ryanvm) → needinfo?(kyle)
From comment 1 it sounded like this bug is specific to "content scaling" which isn't turned on yet for Windows.

FWIW I can reproduce 'tiny controls' bug 820831.
Tiny UI, or content scaling for flash on windows, is bug 820831, not this bug. This is a sub-bug to that one, because when I enable content scaling using the patches in bug 820831, if the plugin is windowed, the width/height of the window does not scale correctly. I'll forward you both the email that might explain that more.
Flags: needinfo?(kyle)
Would like to request status update and an ETA for the bug fix, if available.
Marking this as a duplicate of Bug 820831 as the work really should just happen there.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.