Last Comment Bug 664165 - move editor/libeditor/html/tests/test_contenteditable_text_input_handling.html to mochitest-chrome
: move editor/libeditor/html/tests/test_contenteditable_text_input_handling.htm...
Status: RESOLVED FIXED
[specialpowers]
:
Product: Core
Classification: Components
Component: Editor (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: Joel Maher ( :jmaher)
:
: Makoto Kato [:m_kato]
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-14 09:20 PDT by Joel Maher ( :jmaher)
Modified: 2011-06-19 17:24 PDT (History)
0 users
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
move test_contenteditable_text_input_handling.html to mochitest-chrome (1.0) (3.12 KB, patch)
2011-06-14 09:22 PDT, Joel Maher ( :jmaher)
masayuki: review+
Details | Diff | Splinter Review

Description Joel Maher ( :jmaher) 2011-06-14 09:20:40 PDT
in preparation for turning on specialpowers, we are moving a lot of tests that use a lot of enablePrivilege to mochitest-chrome.  This is only the case if the test will gain the same test coverage.
Comment 1 Joel Maher ( :jmaher) 2011-06-14 09:22:58 PDT
Created attachment 539230 [details] [diff] [review]
move test_contenteditable_text_input_handling.html to mochitest-chrome (1.0)

Masayuki, can you review this patch and verify that it will get the same test coverage if run as a mochitest-chrome test?
Comment 2 :Ehsan Akhgari 2011-06-14 14:30:56 PDT
Comment on attachment 539230 [details] [diff] [review]
move test_contenteditable_text_input_handling.html to mochitest-chrome (1.0)

This looks fine to me, but I'll let Masayuki comment too.
Comment 3 Masayuki Nakano [:masayuki] (Mozilla Japan) 2011-06-14 19:24:31 PDT
Comment on attachment 539230 [details] [diff] [review]
move test_contenteditable_text_input_handling.html to mochitest-chrome (1.0)

looks ok.
Comment 4 Joel Maher ( :jmaher) 2011-06-19 17:24:45 PDT
http://hg.mozilla.org/mozilla-central/rev/d8b8e75bc4ab

Note You need to log in before you can comment on or make changes to this bug.