Closed Bug 265416 Opened 21 years ago Closed 21 years ago

Image properties dialog doesn't show image preview

Categories

(SeaMonkey :: Composer, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: boofy_bloke, Assigned: bzbarsky)

References

Details

(Keywords: regression)

Attachments

(2 files, 1 obsolete file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041018 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041018 It flicks in for an instant and then disappears. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Confirming, didn't find a dupe or that this is expected behaviour.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ths regressed between 2004-09-11(-05) and 2004-09-14(-06).
Keywords: regression
OS: Windows XP → All
The bug is probably related to the computed width of the description box sitting above the image itself in the dialog. It should be more or less 50 pixels (I see 51px in Nvu (based on 1.7.1) and old versions of Composer) while I see the real size of the image in the more recent builds.
Ok, this is a severe regression in the user-friendlyness of Composer/Nvu and I think it should be considered as a UI blocker.
Flags: blocking1.8a5?
What are the steps to reproduce here? (The ones missing from comment 0.) I tried loading this page in editor and viewing image properties on the banner at the top of the page in a 2004-10-24-05 build. The preview image is shown. The only difference between the Sept 11 and Sept 13 build is the vertical alignment of the image -- in the latter build it's shifted up a bit more.
(In reply to comment #7) > What are the steps to reproduce here? (The ones missing from comment 0.) > > I tried loading this page in editor and viewing image properties on the banner > at the top of the page in a 2004-10-24-05 build. The preview image is shown. > The only difference between the Sept 11 and Sept 13 build is the vertical > alignment of the image -- in the latter build it's shifted up a bit more. in a 2004-10-21 build, I was immediately able to reproduce the bug: 1. Launch composer 2. click on insert image 3. click on the Browse button to select a local image file 4. the dialog should show the image preview and does not
Ah, ok. Sounds like a totally different codepath from the one I was testing... I'll check this out tonight, I guess.
Attached file Testcase, I think. (obsolete) —
The green box should more or less shrink-wrap the little image. It doesn't. Note that making the little image display:block makes it work. Also note that messing with display of the hbox or description will make it work too.
Attached file Even more minimal
Attachment #163450 - Attachment is obsolete: true
So the testcase shows what seems to be an incremental reflow problem in XUL. Basically, reflowing the image reduces the size of the image but does not reduce the size of the <description> containing the image. If I remove the max-width and max-height, then reducing the size of the image doesn't even work (as in,the image is still rendered 200px tall by 400px wide, in spite of onload setting its width and height). I'm not sure what suddenly exposed this incremental reflow bug in the editor case, but here we are. Again, making the image be a block helps, so editor can use that as a workaround. I'm attaching a patch that uses the other workaround -- collapsing the image holder while the image loads and uncollapsing onload, so that reflow happens correctly....
Attachment #163457 - Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #163457 - Flags: review?(daniel)
Regression window: 2004080605 -- 2004081000, (bug 230170 looks closest to me)
Comment on attachment 163457 [details] [diff] [review] Workaround XUL issue >+ // XXXbz that bug is long-since fixed. Is this still needed? You mean, that we should reuse a predefined image? Sure, I additionally tried patching that and it seems to work fine - and I even discovered a harmless bug in the code while rewriting it.
Attachment #163457 - Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
Bug 230170 could well have exposed bugs in the reflow code by changing ordering of things, yes. > You mean, that we should reuse a predefined image? Yep. I'll file a followup bug to that effect.
Comment on attachment 163457 [details] [diff] [review] Workaround XUL issue r=daniel@glazman.org Please just add a comment line saying this is a workaround for bug 265416 ; we should not need this patch.
Attachment #163457 - Flags: review?(daniel) → review+
Assignee: composer → bzbarsky
Filed bug 266284 on the XUL issue and bug 266286 on removing the other workaround in this code. Checked in, with the comment Daniel asked for added.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
*** Bug 266802 has been marked as a duplicate of this bug. ***
Flags: blocking1.8a5?
Product: Browser → Seamonkey
Blocks: 230170
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: