Enable test_clipboard_events.html in e10s

RESOLVED FIXED in Firefox 48

Status

()

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: enndeakin, Assigned: enndeakin)

Tracking

(Blocks: 1 bug)

unspecified
mozilla48
Points:
---

Firefox Tracking Flags

(e10s+, firefox48 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
Created attachment 8716976 [details] [diff] [review]
test_clipboard_events
Blocks: 984139
tracking-e10s: ? → +
(Assignee)

Updated

3 years ago
Attachment #8716976 - Flags: review?(bugs)
(Assignee)

Updated

3 years ago
Attachment #8716976 - Flags: review?(bugs) → review?(mrbkap)
Comment on attachment 8716976 [details] [diff] [review]
test_clipboard_events

Review of attachment 8716976 [details] [diff] [review]:
-----------------------------------------------------------------

I have a couple of questions/comments, but r=me if you don't want to do them.

::: dom/tests/mochitest/general/test_clipboard_events.html
@@ +56,5 @@
> +  test_input_copy_button_dataTransfer,
> +  test_eventspref_disabled
> +  ];
> +
> +function doTests()

I don't know if it's worth it for you, but I've been using SpawnTask.js and spawn_task(generator_function) to avoid re-implementing this wheel. That would also mean that you could do:

function* doTests() {
  // init

  for (test of testFunctions) {
    yield test();
  }

  // cleanup.
}

which is cleaner.

@@ +525,5 @@
>  
>  function test_eventspref_disabled() {
>    // Disable clipboard events
> +  return new Promise(resolve => {
> +    SpecialPowers.pushPrefEnv({"set": [['dom.event.clipboardevents.enabled', false]]}, doPrefDisabledTest);

I wonder if we should add some promise-based pref functions to SpecialPowers.
Attachment #8716976 - Flags: review?(mrbkap) → review+
Are this and bug 1246662 ready to land?

Comment 4

3 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/2338e962df6d
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
status-firefox48: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
You need to log in before you can comment on or make changes to this bug.