Closed Bug 305673 Opened 19 years ago Closed 19 years ago

Problems redrawing bottom margin

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: infinity0x, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

When a margin is set dynamically (using JS), the bottom margin is not redrawn.

More specifically: when a (?CSS class)? is added to a (?block-level) element

I havent tested setting the margin directly yet, nor testing it on inline elements

Reproducible: Always

Steps to Reproduce:
1.Go to http://webxl.5gigs.com/scratch/bugtest.html
2.Type "t6" into the top text-box and click "addClass"

Actual Results:  
3.Notice the lack of a bottom margin on the test <div>
4.Click the left link.
5.Then, click the right link.

Notice that the left link is static, and does not fix the re-draw. However the
right link is repositioned on :active and this also re-draws the bottom margin.


Expected Results:  
After 2), the bottom margin should have been redrawn and a 20px gap appear
between the bottom white border and the links.
Further information:

Bug doesn't show up for inline elements (partly because the vertical margins are
not set)

Bug DOES show up when setting the margin directly. (see updated page)

Bug is ONLY fixed when :active is repositioned; Positioning the static link
doesn't work.

http://webxl.5gigs.com/scratch/bugtest.html
*** Bug 305674 has been marked as a duplicate of this bug. ***
*** Bug 305671 has been marked as a duplicate of this bug. ***
Seems to worksforme with a one week old SeaMonkey trunk build (mac). Have you
tried it in a more recent build (like Deer park a2)?
(In reply to comment #4)
> Seems to worksforme with a one week old SeaMonkey trunk build (mac). Have you
> tried it in a more recent build (like Deer park a2)?

Ah, yes, it's fixed. Thanks for pointing that out :)
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
per last comment wfm
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.