News for hackers. Stuff that matters.
Re:Intent to Implement: Display Locking by emsy on Thursday September 13, 2018 @04:08PM (#17982065)
No, this is about increasing performance by taking elements out of the slow DOM update cycle
Re:Intent to Implement: Display Locking by phkahler on Thursday September 13, 2018 @04:18PM (#17982152)
>> No, this is about increasing performance by taking elements out of the slow DOM update cycle

The question was not about the intent of the feature, but a possible use case that may not have been intended. A more specific reason for the "No" could be more informative.

Re:Intent to Implement: Display Locking by xg15 on Thursday September 13, 2018 @04:30PM (#17982252)
Interesting idea - though I think any kind of script API can be circumvented by ad blockers pretty easily: They can always inject their own script before anything from the page is executed and manipulate the API functions or replace them with "do nothing" implementations.
[dead]
Re:Intent to Implement: Display Locking by andrestan on Thursday September 13, 2018 @05:53PM (#17982986)
It was a really short doc and I didn't see it answer this question at all. Where do you see it answering it?
Re:Intent to Implement: Display Locking by mbrumlow on Thursday September 13, 2018 @04:41PM (#17982357)
Yup that is it.