Open Bug 842952 Opened 7 years ago Updated 11 months ago

Implement the LightLevelEvent Interface

Categories

(Core :: DOM: Device Interfaces, defect, P3)

defect

Tracking

()

People

(Reporter: Jeremie, Unassigned)

References

()

Details

Attachments

(1 file)

As we have the DeviceLightEvent interface, it would be nice to also have the LightLevelEvent interface.
jeremie, is this something you want to implement?
(In reply to Doug Turner (:dougt) from comment #1)
> jeremie, is this something you want to implement?

I would like to. Unfortunately, I have no time until end of March and I have absolutely no C++ skills at all which make things a little hard (even if it does not seam to difficult regarding the work already done on DeviceLightEvent)

So if no one take it until spring, I'll try to fix it. In the meantime, feel free to take it or to give it to someone else.
Thanks for submitting the bug Jeremie! You beat me to it by a couple of days :)

Anyhow, I'm taking this bug if nobody has other plans.
I just noticed that the interface on the latest editor's draft uses an |enum| instead of a |string|[2].  Should we implement it as an enum?.  This is the only thing that I'm missing to submit a patch for review.

[1]https://dvcs.w3.org/hg/dap/raw-file/tip/light/Overview.html#lightlevelevent-interface
[2]http://www.w3.org/TR/ambient-light/#lightlevelevent-interface
The patch lacks the proper LightLevelEvent interface definition and currently implements it almost exactly like DeviceLight for testing.
i think using the enum is the right thing.
I don't think we need to implement this, unless I'm missing something: http://lists.w3.org/Archives/Public/public-device-apis/2013Apr/0019.html
Jorge, could you update the patch to instead implement this attribute on top of DeviceLightEvent instead? That's the way we want to go forward here.

See http://lists.w3.org/Archives/Public/public-device-apis/2013Apr/0048.html
Hi Anne.  Sure, I'll update the patch. Sorry for the delay, I've had some very busy weeks.
It's been a while.  New job and, sadly, I won't be able to work on this anytime soon.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.