Closed Bug 356084 Opened 18 years ago Closed 7 years ago

PLUGIN: WM_PAINT and Update messages through NPP_HandleEvent give inconsistent coordinates

Categories

(Core Graveyard :: Plug-ins, defect)

1.8 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: fleabix, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04324.17; InfoPath.2)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061003 Firefox/2.0

Mouse coordinates provided by Firefox are incorrect when passed into the plugin through NPP_HandleEvent.

1. When HTML within div tags are changed, the coordinates provided by Firefox do not take into account the location of the plugin relative to the window, but once the window has been resized, it will recalculate to the correct coordinates.

2. When the plugin exists on a page inside a frameset, and is centered by a table/td align="middle", the mouse clicks are always relative to the plugin, and do not take the centering of the plugin into account.

There is no way to tell whether the coordinates are relative to the page, or to the plugin, and the plugin will translate the erroneous coordinates as if they were valid, and get incorrect mouse hit detection.

Both are inconsistent with normal behavior in Firefox.

Reproducible: Always

Actual Results:  
Mouse clicks coordinates are not offset by the location of the plugin

Expected Results:  
Mouse click coordinates are offset by the location of the plugin

The coordinates are never inconsistent in Camino and Safari. Always relative to the page, no matter where the plugin is, and no matter when it's loaded.
Most situations were fixed in nightly.  Reworking plug-in code to remove the workarounds to fully verify.
Ok, please resolve as worksforme if these issues are indeed fixed on trunk. Otherwise please confirm which issues still exist in a trunk build.
Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Version: unspecified → 1.8 Branch
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.