Open Bug 132577 Opened 23 years ago Updated 2 years ago

when typing an object will briefly be redrawn in the wrong place

Categories

(Core :: Layout, defect, P4)

x86
Windows NT
defect

Tracking

()

Future

People

(Reporter: will, Unassigned)

References

()

Details

(Whiteboard: DUPEME)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.9) Gecko/20020311 BuildID: 2002031104 This page has an svg imbedded at the top. Then under that a div is floated to the left which contains a form and another svg below that. As elements of the form are typed in (or buttons clicked) the lower svg will render moved up into the upper image. It is just a flicker and can be most easily observed while typing steadily. The svg's are being rendedered by version 2 of adobe's plugin, but since they are rendering over top of the form which is not controlled by the plugin it is unlikely that it is a plugin error. Reproducible: Always Steps to Reproduce: 1. Type in the login box Actual Results: The button list flickers over the login box and part of the title image. Expected Results: The button list should stay where it was originally. Also, there is a input:focus color style that is applied to the buttons, but not to the text boxes. Also, the border for the text areas is rendered using the color style unless an explicit border-color style is specified. To the best of my knowledge the border-color style is the only one that is supposed to affect the border color.
Looks like this is due to the reflows when we type...
Assignee: rods → attinasi
Component: HTML Form Controls → Layout
QA Contact: madhur → petersen
Whiteboard: DUPEME
Changing QA contact
QA Contact: petersen → moied
Using build ID 20020322 on WINXP, cant even able to see button list and title image.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4
Target Milestone: --- → Future
reporter (Will), the page cannot be accessed (log-in required). Can you attach the testcase here?
Assignee: attinasi → nobody
QA Contact: moied → layout
I think we can now close this 8 years old bug.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.