On 8/7/17 11:28 AM, Enrico Weigelt, metux IT consult wrote:
hmm, then what are the partial interfaces actually for ?
They're for use in specifications that want to add things to an existing
interface. They're a specification device, basically.
I had the impression that distributing (potent
On 07.08.2017 17:17, Boris Zbarsky wrote:
Can I move that stuff to a separate webidl file, which is only
added in dom/webidl/moz.build when wakelocks enabled ?
(so no #ifdef's in Navigator.webidl needed)
If you try to do this, you will get a message from binding codegen that
explicitly says t
On 8/6/17 3:56 PM, Enrico Weigelt, metux IT consult wrote:
is there a way to use the partial interfaces for build-time
configurable features ?
Not without #ifdef.
Can I move that stuff to a separate webidl file, which is only
added in dom/webidl/moz.build when wakelocks enabled ?
(so no #ifde
On 07.08.2017 10:31, Gabriele Svelto wrote:
On 06/08/2017 21:56, Enrico Weigelt, metux IT consult wrote:
For example, I'm currently working on making the whole wakelock
stuff optional (eg. only built on android). Navigator.webidl
references MozWakeLock, which wouldn't exist w/o wakelocks.
Do y
On 06/08/2017 21:56, Enrico Weigelt, metux IT consult wrote:
> For example, I'm currently working on making the whole wakelock
> stuff optional (eg. only built on android). Navigator.webidl
> references MozWakeLock, which wouldn't exist w/o wakelocks.
Do you mean navigator.requestWakeLock()? That'
Hi folks,
is there a way to use the partial interfaces for build-time
configurable features ?
For example, I'm currently working on making the whole wakelock
stuff optional (eg. only built on android). Navigator.webidl
references MozWakeLock, which wouldn't exist w/o wakelocks.
Can I move that
6 matches
Mail list logo
