Closed
Bug 304078
Opened 19 years ago
Closed 19 years ago
Resize and keyboard events not firing in imageDocument with 'resize large images' enabled.
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: pythonesque+bugzilla, Unassigned)
References
()
Details
(Keywords: fixed1.8, regression, testcase)
Attachments
(1 file)
1.73 KB,
patch
|
mrbkap
:
review+
brendan
:
superreview+
brendan
:
approval1.8b4+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050809 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050809 Firefox/1.0+ When "Resize large images to fit in browser window" is checked, when viewing an image larger than one's browser window, the keyboard shortcuts for zooming in and out (+, -) do not trigger a zoom. Additionally, if the browser window is resized while the image is zoomed out, the image does not resize to match the window. Reproducible: Always Steps to Reproduce: 1. Go to Tools -> Options -> Advanced -> General, and check "Resize large images to fit in browser window." Alternatively, go to about:config and set browser.enable_automatic_image_resizing equal to true. 2. Set your browser to a resolution less than that of 1024 x 768. 3. Go to http://weblogs.mozillazine.org/hyatt/images/clean/header_title_blue.jpg. 4. Try to zoom in by using +, then out by using -. 5. Resize the window to another size smaller than the current one. Actual Results: 4. The image did not change size. 5. The image did not resize. Expected Results: 4. The image should have zoomed in on +, zoomed back out on -. 5. The image should have resized to fit in the smaller window. This is not a bfcache bug. It's possible that it's fallout from the split window landing; I'm not sure. The click event does work, though.
Comment 1•19 years ago
|
||
Regressed between 2005-07-30 and 2005-07-31, so indeed very likely fall-out from bug 296639.
Comment 2•19 years ago
|
||
nsImageDocument::SetScriptGlobalObject() registers events on the global, and right after the window calls that method, it "restores" the listener manager from the old window (or null in cases where we don't want to preserve event handlers between document transitions, which is most cases) and blows away the one where the listeners we just registerd in. This simply reorders the code so that we don't loose listeners.
Attachment #192513 -
Flags: superreview?(brendan)
Attachment #192513 -
Flags: review?(mrbkap)
Comment 3•19 years ago
|
||
Comment on attachment 192513 [details] [diff] [review] Fix. r=me
Attachment #192513 -
Flags: review?(mrbkap) → review+
Comment 4•19 years ago
|
||
Comment on attachment 192513 [details] [diff] [review] Fix. sr=me, if someone in the know on branching wants to approve, this could go in before the branch is cut. Not a big deal either way. /be
Attachment #192513 -
Flags: superreview?(brendan)
Attachment #192513 -
Flags: superreview+
Attachment #192513 -
Flags: approval1.8b4+
Comment 5•19 years ago
|
||
Fixed by the checkin for bug 303267.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•