Closed
Bug 38825
Opened 25 years ago
Closed 23 years ago
ListControlFrame::AddOption called before option added to DOM
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
INVALID
Future
People
(Reporter: rods, Assigned: john)
References
Details
AddOption gets called on the ListControlframe before it is actually added in the
DOM. The notification is sort of a side affect of the SetParent call in the
OptionElement. We have talked about fixing this in the past, well here is a bug
so we don't forget.
Comment 2•25 years ago
|
||
Rod, does this cause nasty side-effects? Marking Future in hopes that it
doesn't.
Target Milestone: M17 → Future
Reporter | ||
Comment 3•25 years ago
|
||
I thought this was fixed recently, except for a minor change I needed to make
which is why I reopened Bug #44266. So I think this bug can be marked fixed.
Comment 5•24 years ago
|
||
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
Comment 6•24 years ago
|
||
Clarifying summary
Status: NEW → ASSIGNED
Summary: Notification to frame happens before element is added in DOM → ListControlFrame::AddOption called before option added to DOM
SPAM. HTML Element component deprecated, changing component to Layout. See bug
88132 for details.
Component: HTML Element → Layout
Assignee | ||
Comment 9•23 years ago
|
||
This still happens in the bug 34297 rewrite (and there are specific reasons for
it), but there are zero side-effects I can think of. Essentially, AddOption()
is now called *after* the option is added to the options[] list but *before* it
is added as an HTML child of the <select> element.
AddOption() has become more a notification than a request for action to add an
option. From my reading of the code, this shouldn't have any adverse effects.
In fact, I'm considering removing it entirely, along with all the annoying timer
stuff. I could just make this the bug where I do that. (We'll discuss first; I
can't be 100% certain there are no repercussions yet, that's why I haven't done
it already.)
Does anyone have a problem with me taking this bug? pollmann, are you still
working on it?
Depends on: 34297
Comment 10•23 years ago
|
||
Bulk reassigning form bugs to Alex
Assignee: pollmann → alexsavulov
Status: ASSIGNED → NEW
Comment 11•23 years ago
|
||
John:
if you want to take care of this bug just go ahead and reassign it to you.
I add me on the cc list please.
Assignee | ||
Comment 13•23 years ago
|
||
Marking invalid. ListControlFrame::AddOption is all but irrelevant now, and is
nothing but a notification. Its counterpart is now
nsHTMLSelectElement::WillAddOptions(), which is much more clearly named and
doesn't run on a timer to boot.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•