Closed Bug 373308 Opened 19 years ago Closed 19 years ago

Resizing a popup with an enlarged image in it generates strange quircks

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

Product:
Core
Component:
Layout: Images, Video, and HTML Frames
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: sjon, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070224 BonEcho/2.0.0.2 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070224 BonEcho/2.0.0.2 When resizing a popup with only an image in it; when the popup is smaller then the image; the image will be resized. When using the magnifier to enlarge the image; and then resize the popupwindow strange quircks will appear. Also; the image will not fully appear although the required space is available Reproducible: Always Steps to Reproduce: 1. Open a new window with an image 2. Use the magnifier to enlarge the image 3. Resize the popup to be bigger then the image and see some strange render-issues Actual Results: Strange render quirck as shown on the given URL Expected Results: Image should move when space is available so the full image is visible. Magnifier glass-option should disappear when moving over the expanded image
Windows & Mac shows no problems; another linux machine shows the same problem. The magnifier behaviour is however inconstent on those platforms as well; allthough [+] is available; [-] never shows up after enlarging
This sounds (and behaves) like a dupe of / related to Bug 369370. Marking it depending.
Depends on: 369370
Component: General → Layout: Images
Product: Firefox → Core
QA Contact: general → layout.images
Version: unspecified → Trunk
(In reply to comment #2) > This sounds (and behaves) like a dupe of / related to Bug 369370. > Marking it depending. That is just the magnifier part; I don't see the same strange render issues that appears in this bug [which actually seems like a memory error to me].
Nope; it is fixed in trunk
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
No patch / bug referenced as the fix.
Resolution: FIXED → WORKSFORME
How would I know which patch has fixed this?
Product: Core → Core Graveyard
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.