Closed
Bug 750439
Opened 13 years ago
Closed 6 years ago
SecReview: Implement DOM3 composition events
Categories
(mozilla.org :: Security Assurance: Review Request, task)
mozilla.org
Security Assurance: Review Request
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: curtisk, Assigned: jruderman)
References
Details
(Whiteboard: [pending secreview][start yyyy-mm-dd][target yyyy-mm-dd][score:0::Low][Fx])
SecReview tracking bug
Actions regarding the review of the dependent bug should be tracked here.
Assignee | ||
Comment 1•13 years ago
|
||
If I copy the pattern in https://bug543789.bugzilla.mozilla.org/attachment.cgi?id=561673 into the DOM fuzzer, will I be testing the right thing? Or do I need to somehow test with actual IMEs, or without (content) JS on the stack?
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → NEW
Reporter | ||
Comment 2•13 years ago
|
||
This bug is assigned so I am perplexed as to why it is new and not assigned?
Assignee | ||
Comment 3•13 years ago
|
||
Traditionally, ASSIGNED means the assignee is actively working on it.
Comment 4•13 years ago
|
||
(In reply to Jesse Ruderman from comment #1)
> If I copy the pattern in
> https://bug543789.bugzilla.mozilla.org/attachment.cgi?id=561673 into the DOM
> fuzzer, will I be testing the right thing? Or do I need to somehow test with
> actual IMEs, or without (content) JS on the stack?
We can test the IME handling only for XP part by automated tests. E.g., for DOM event firing, editor behavior and so on. For testing widget part and/or combination with platform APIs or IMEs, we need the environment actually.
Assignee | ||
Comment 5•13 years ago
|
||
Do we have any such tests?
Comment 6•13 years ago
|
||
For the former, yes.
http://mxr.mozilla.org/mozilla-central/source/widget/tests/window_composition_text_querycontent.xul
http://mxr.mozilla.org/mozilla-central/source/widget/tests/window_imestate_iframes.html?force=1
http://mxr.mozilla.org/mozilla-central/source/widget/tests/test_input_events_on_deactive_window.xul
http://mxr.mozilla.org/mozilla-central/source/editor/libeditor/text/tests/test_dom_input_event_on_texteditor.html?force=1
http://mxr.mozilla.org/mozilla-central/source/editor/libeditor/html/tests/test_dom_input_event_on_htmleditor.html?force=1
For the latter, no. We need to test manually.
Reporter | ||
Comment 7•12 years ago
|
||
Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings
Priority: N/A
Operational: 0 - N/A
User: 0 - N/A
Privacy: 0 - N/A
Engineering: 2 - Normal
Reputational: 0 - N/A
Priority Score: 0
Whiteboard: [pending secreview] → [pending secreview][start yyyy-mm-dd][target yyyy-mm-dd][score:0::Low]
Updated•12 years ago
|
Whiteboard: [pending secreview][start yyyy-mm-dd][target yyyy-mm-dd][score:0::Low] → [pending secreview][start yyyy-mm-dd][target yyyy-mm-dd][score:0::Low][Fx]
Comment 8•6 years ago
|
||
Jason, does Domino test these events? See e.g. comment 6. If this is covered by Domino, please just close this bug as FIXED. Thanks!
Flags: needinfo?(jkratzer)
Comment 9•6 years ago
|
||
(In reply to Christian Holler (:decoder) from comment #8)
Jason, does Domino test these events? See e.g. comment 6. If this is covered by Domino, please just close this bug as FIXED. Thanks!
Domino covers this in the context of non-privileged JS. Anything involving access to special powers (i.e. synthesizeCompositionChange) is not covered.
Flags: needinfo?(jkratzer)
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•