Re: [whatwg/fullscreen] Add keyboard locking option (PR #232)

saschanaz left a comment (whatwg/fullscreen#232)

But it'll be all fullscreen options, why do we need those attributes to be directly in document?

Was also thinking about:

```js
document.fullscreen.keyboardLock
// meaning making fullscreen not a boolean anymore
// less attribute pollution to document
// unless anyone is doing `document.fullscreen == true`....

const resultingOptions = await document.requestFullscreen(options);
resultingOptions.keyboardLock // less hacky way than abusing getter
```

> Is there a use case?

Maybe also feature detection?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/232?email_source=notifications&email_token=ACLYVMID7VMIRHRHNEZCK4T4XHS5DA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMZQGM2DQNRQHAZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4303486083
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/pull/232/c4303486083@github.com>