Closed Bug 22270 Opened 26 years ago Closed 26 years ago

Text field in profile-"wizard" changes size on click

Categories

(Core :: XUL, defect, P2)

defect

Tracking

()

VERIFIED DUPLICATE of bug 29198

People

(Reporter: faetterd, Assigned: eric)

References

Details

In step two of the profile-wizard, the textfield (defaulted to "myMozilla") has a little bug. If you highlight/markup the text in the field, it resizes to about 20% of its original size...
Assignee: nobody → syd
You seem to have some sparetime :o)
Assignee: syd → trudelle
Component: Profile → XP Toolkit/Widgets
Product: Architecture → Browser
Version: 5.0 → other
XPToolkit bug it seems, reassigning to Peter so it can be triaged.
Assignee: trudelle → beppe
Component: XP Toolkit/Widgets → Editor
textfields are not XPToolkit widgets, changing component to Editor, reassigning.
Assignee: beppe → buster
Target Milestone: M13
assigning to buster -- this sounds like a dup of one that is already in your list (21177 or 21919)
Assignee: buster → evaughan
OS: Linux → All
Priority: P3 → P2
Hardware: PC → All
Summary: Text field in profile-"wizard"... → Text field in profile-"wizard" changes size on click
I think this is a box layout bug. I think nsGfxTextControlFrame::Reflow() is doing the right thing, given the input it recieves. All form controls size themselves according to their reflow state's mComputedWidth data. See nsFormControlFrame::GetStyleSize(). The relevant code is: if (aReflowState.mComputedWidth != NS_INTRINSICSIZE) { aSize.width = aReflowState.mComputedWidth; // you've been given a width } else { aSize.width = CSS_NOTSET; // figure out your own width } In the test case for this bug, during initial reflow mComputedWidth is NS_INTRINSICSIZE and the text control decides it should be 2160 twips wide. Then in the resize reflow, mComputedWidth is set to a value (5628). The text control sees this and uses it directly. This is how it displays initially. Clicking on the text control generates an incremental reflow. mComputedWidth is again NS_INTRINSICSIZE, so the text control again compuates its own width to 2160, and displays more narrow. I don't know how to read BOX XUL, so I don't know what the intended size is here (wider or more narrow.) But it's pretty clear that mComputedWidth should be the same for resize and incremental reflows in this case. However, it is the box layout code that's generating the reflow state that is ultimately used in the text control, so I think the bug must be there. I traced this back into nsBoxFrame::FlowChildAt(), but I don't know enough about the code to go much further without some pain.
*** Bug 21919 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: M13 → M14
pushing to m14
Component: Editor → XP Toolkit/Widgets
changing component to XP Toolkit
Target Milestone: M14 → M15
retargeting
*** This bug has been marked as a duplicate of 29198 ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*spam* changing qa contact from nobody@mozilla.org to me (BlakeR1234@aol.com) on 121 open or resolved (but not verified) bugs. sorry for the spam everybody, but most of these bugs would just remain dormant and not checked by QA otherwise. I'm not sure how so many bugs have nobody as their QA contact, but I suspect this is the fault of some sort of bugzilla corruption that happened at some point (most of these bugs are in the 20000-26000 range, and I don't see where in the activity log that QA contact explicitly changed to nobody@mozilla.org) Anyways, sorry again for spam. If you really get annoyed, I'm usually available in #mozilla on IRC for torture.
QA Contact: nobody → BlakeR1234
Verified duplicate.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.