Closed
Bug 632428
Opened 15 years ago
Closed 15 years ago
"Fix the caller!" when datalist fires onselect on a node created from a chrome context
Categories
(Toolkit :: Form Manager, defect)
Toolkit
Form Manager
Tracking
()
RESOLVED
FIXED
mozilla2.0b12
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | final+ |
| status1.9.2 | --- | unaffected |
| status1.9.1 | --- | unaffected |
People
(Reporter: mak, Assigned: mounir)
References
Details
(Keywords: regression, Whiteboard: [sg:critical?][hardblocker])
Attachments
(3 files)
|
14.09 KB,
text/plain
|
Details | |
|
2.00 KB,
patch
|
smaug
:
review+
Dolske
:
review+
|
Details | Diff | Splinter Review |
|
7.08 KB,
patch
|
Dolske
:
review+
|
Details | Diff | Splinter Review |
I have a datalist in content context, chrome context fills it up with some <option> through a remote url that content doesn't have access to.
let list = contentDoc.getElementById("mydatalist");
let value = "xyz";
list.appendChild(
list.ownerDocument.createElement("option")
).value = value;
when the datalist shows the node I created gets a onselect event, and this triggers a "WARNING: fix the caller!"
Smaug asked be to file the bug with a full stack
| Reporter | ||
Comment 1•15 years ago
|
||
| Reporter | ||
Comment 2•15 years ago
|
||
looking at local values I found a "onselect" in event userType and a "tree" in the target
Comment 3•15 years ago
|
||
Seems like the not-so-safe AttributeChanged handling was added in Bug 556007.
Blocks: 556007
Keywords: regression
Comment 4•15 years ago
|
||
And this isn't only about AttributeChanged, but all the
mutation observer method.
We should probably use a script runner to call RevalidateDataList();
| Reporter | ||
Comment 5•15 years ago
|
||
to reproduce the stack you can use "experiment 2.1" patch in bug 612453, it adds a autocomplete datalist to about:home search field. Just type in the search field to activate autocomplete and you'll see the warnings.
| Assignee | ||
Comment 6•15 years ago
|
||
This patch is fixing the issue. I guess this is because OnUpdateSearchResult was called from nsIMutationObserver methods.
Assignee: nobody → mounir.lamouri
Status: NEW → ASSIGNED
Attachment #511053 -
Flags: review?(Olli.Pettay)
| Assignee | ||
Updated•15 years ago
|
Version: unspecified → Trunk
| Assignee | ||
Updated•15 years ago
|
status1.9.1:
--- → unaffected
status1.9.2:
--- → unaffected
Updated•15 years ago
|
Attachment #511053 -
Flags: review?(dolske)
Attachment #511053 -
Flags: review?(Olli.Pettay)
Attachment #511053 -
Flags: review+
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [needs review dolske]
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [needs review dolske] → [needs review dolske][needs try]
| Assignee | ||
Comment 7•15 years ago
|
||
Why this bug has been marked "security-sensitive"?
| Reporter | ||
Comment 8•15 years ago
|
||
Smaug asked me to mark it as security sensitive while it was investigated.
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [needs review dolske][needs try] → [needs review dolske][passed try]
| Assignee | ||
Comment 9•15 years ago
|
||
Attachment #511331 -
Flags: review?(Olli.Pettay)
Comment 10•15 years ago
|
||
(In reply to comment #7)
> Why this bug has been marked "security-sensitive"?
Because nsAutoCompleteController::OnUpdateSearchResult is called at unsafe time,
and that method seems to trigger some scripts to run.
If those script can include anything in content page, this would be probably
sg:critical.
| Assignee | ||
Comment 11•15 years ago
|
||
(In reply to comment #10)
> (In reply to comment #7)
> > Why this bug has been marked "security-sensitive"?
>
> Because nsAutoCompleteController::OnUpdateSearchResult is called at unsafe
> time,
> and that method seems to trigger some scripts to run.
> If those script can include anything in content page, this would be probably
> sg:critical.
I don't think nsAutoCompleteController::OnUpdateSearchResult can trigger any content script.
Comment 12•15 years ago
|
||
sg:critical, just to be on the safe side. Let's get this landed!
blocking2.0: --- → final+
Whiteboard: [needs review dolske][passed try] → [sg:critical?][hardblocker][needs review dolske][passed try]
Updated•15 years ago
|
Attachment #511053 -
Flags: review?(dolske) → review+
Updated•15 years ago
|
Attachment #511331 -
Flags: review+
| Assignee | ||
Updated•15 years ago
|
Attachment #511331 -
Flags: review?(Olli.Pettay)
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [sg:critical?][hardblocker][needs review dolske][passed try] → [sg:critical?][hardblocker][passed try][needs landing]
Updated•15 years ago
|
Whiteboard: [sg:critical?][hardblocker][passed try][needs landing] → [sg:critical?][hardblocker][passed try][needs landing][has patch]
| Assignee | ||
Comment 13•15 years ago
|
||
Pushed:
http://hg.mozilla.org/mozilla-central/rev/23703ec8b73b
http://hg.mozilla.org/mozilla-central/rev/5a9359bc00f6
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [sg:critical?][hardblocker][passed try][needs landing][has patch] → [sg:critical?][hardblocker]
Target Milestone: --- → mozilla2.0b12
Updated•15 years ago
|
blocking2.0: final+ → ---
Updated•15 years ago
|
blocking2.0: --- → final+
Updated•11 years ago
|
Group: core-security → core-security-release
Updated•10 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•