Closed
Bug 406717
Opened 17 years ago
Closed 1 month ago
[meta] Audit all uses of window frames for resolution-independence-unsafe assumptions
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: stuart.morgan+bugzilla, Unassigned)
References
Details
Window frame coordinate systems cannot be assumed to be the same as those of view (and therefore Gecko) coordinates. We violate this in a bunch of places; from a very rough first pass, this likely includes: - window sizing and positioning from Gecko (BrowserWrapper's sizeBrowserTo:, CHBrowserListener's Get/SetDimensions) - sizing and positioning of AutoCompleteTextField's dropdown - tooltip positioning - hideChangePasswordField in BrowserSecurityDialog The above is just from looking at setFrame:; there's almost undoubtedly more where we get and do computation with the window frame. I'll file a bug for the first, which I've verified and started to fix, and we can file more as we verify them.
Reporter | ||
Comment 1•17 years ago
|
||
Oops, forgot the reference: http://developer.apple.com/documentation/UserExperience/Conceptual/HiDPIOverview/HiDPISupport/chapter_3_section_2.html
Reporter | ||
Updated•16 years ago
|
Target Milestone: --- → Camino2.0
Reporter | ||
Comment 2•16 years ago
|
||
This is probably low-priority for 2.0 given that OS-level resolution independence has problems in Gecko 1.9.0, but it would be good to get our stuff in order if we have time.
Reporter | ||
Comment 3•16 years ago
|
||
... which we don't realistically.
Target Milestone: Camino2.0 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•