Open Bug 1056478 Opened 10 years ago Updated 10 months ago

Resizer of sub-dialog follows only half of the movement of mouse pointer

Categories

(Firefox :: Settings UI, defect, P3)

34 Branch
defect

Tracking

()

People

(Reporter: alice0775, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: polish)

Steps To Reproduce:
1. Open any resizable sub-dialog of the in- content preferences
2. Attempt to resize by mouse dragging

Actual Results:
The resizer follows only half of the movement of mouse pointer

Expected Results:
The resizer should follow the movement of the mouse. (i.e., The resizer should be at the position of the mouse pointer)
Keywords: polish
[Tracking Requested - why for this release]: regression
in-content prefs is not shipping in 34. Dropping tracking.
I don't think this blocks the in-content prefs from being shipped. It is something we should fix though.
No longer blocks: ship-incontent-prefs
OS: Windows 7 → All
Hardware: x86_64 → All
During triage we had decided to keep this on the blocker list.
This is a bug that affects all firefox resizers. If you resize a text area, you'll get the same problem.
(In reply to Tim Nguyen [:ntim] from comment #5)
> This is a bug that affects all firefox resizers. If you resize a text area,
> you'll get the same problem.

That's not entirely true. The problem exists with all *centered* textareas. For example, the problem does not reproduce with:
data:text/html,<textarea></textarea>

But does reproduce with:
data:text/html,<center><textarea></textarea>

(copy and paste those in to the address bar and hit Enter)
I filed bug 1105906 to cover the general issue here. We kept it as a blocker for IcP because it is pretty noticeable with the preferences, even though it is not a new regression.
De-listing this from the hard-blocker bug tracking since this bug only uncovers an already existing issue in the platform and this is a polish-related bug that doesn't prohibit usage of the in-content preferences.
Blocks: 718011
No longer blocks: ship-incontent-prefs
Severity: normal → N/A
Priority: -- → P3
Severity: N/A → S3
You need to log in before you can comment on or make changes to this bug.