Closed
Bug 672479
Opened 13 years ago
Closed 13 years ago
ASSERTION: Percentage padding on value div?: 'Error'
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 584564
People
(Reporter: MatsPalmgren_bugz, Unassigned)
Details
(Keywords: assertion, testcase)
STEPS TO REPRODUCE 1. load layout/forms/crashtests/590302-1.xhtml 2. Print Preview ACTUAL RESULTS ###!!! ASSERTION: Percentage padding on value div?: 'Error', file layout/forms/nsTextControlFrame.cpp, line 277 PLATFORMS AND BUILDS TESTED Bug occurs in a local Firefox debug build on Linux x86-64
Comment 1•13 years ago
|
||
The first interesting assert I get here is actually this: ###!!! ASSERTION: Cannot bind twice, need to unbind first: '!mBoundFrame', file ../../../../../mozilla/content/html/content/src/nsTextEditorState.cpp, line 1042 Not sure whether it causes the other. The rest of the asserts I get are because there's an nsTextControlFrame around whose first child is null. The percentage padding assert actually asserts that the child is non-null and has fixed padding, and fails because the first child is null. So how are we ending up in a situation with a null child there?
Comment 2•13 years ago
|
||
Ah, we end up there because the BindToFrame call in CreateAnonymousContent fails, and then we return error from there, but CSSFC doesn't treat failure to create anonymous content as a reason to not create the frame....
Comment 3•13 years ago
|
||
So I bet what's happening here is that we're replicating the fixed textarea across pages, which means we're ending up with multiple nsTextControlFrames for a single textarea node. At some point we had a plan for handling this mess with fixed frames that can't really be replicated.... but I can't remember what that plan was.
That's about as much as I remember :-)
Comment 5•13 years ago
|
||
(In reply to comment #3) > So I bet what's happening here is that we're replicating the fixed textarea > across pages, which means we're ending up with multiple nsTextControlFrames > for a single textarea node. At some point we had a plan for handling this > mess with fixed frames that can't really be replicated.... but I can't > remember what that plan was. Wallpapering the issue with null checks. :((
Comment 6•13 years ago
|
||
That is, my way of saying that, we don't have a good way of fixing this without bug 584564 being fixed (see bug 578604 for the background).
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•