Consider not defining a custom WakeLockEvent

[reillyeon]

Reading the TAG design principles I noticed § 3.7. State and Event subclasses which recommends against creating custom Event subclasses and instead capturing state in the target parameter.

Example code with current API,

let lock = await navigator.wakeLock.request({ type: "script" });
lock.addEventListener('release', e => {
  console.log(`${e.lock.type} wake lock has been released`);
});

Since the event is already fired on lock the lock attribute on the event could be removed, resulting in this code,

let lock = await navigator.wakeLock.request({ type: "script" });
lock.addEventListener('release', e => {
  console.log(`${e.target.type} wake lock has been released`);
});

[reillyeon]

CC @marcoscaceres who was there when we defined WakeLockEvent and maybe missed that target and lock would have the same value or has a good reason not to rely on it.

[marcoscaceres]

Yes, great point @reillyeon. We just need a simple Event.