DOMPreferences was introduced (but it's not landed yet because of some
mochitest failures) to cleanup how preferences are managed by workers.
Preferences getters/setters are main-thread only and, currently, in order
to propagate a white-list of prefs [1], we have to dispatch runnables to
any activ
On 18/12/2017 03:38, Nicholas Nethercote wrote:
I am working on a redesign that will fix a lot of the problems. There was a
meeting about this in Austin. I hope to implement this in Q1 2018.
Yay!
If you have changes related to Prefs, please let me (or another Prefs peer)
know about it. Thanks
Hi,
I recently became the module owner of Prefs, and there are several peers.
In the past it was an ill-maintained module, but that is no longer the case.
I have been doing a bunch of work to improve Prefs. As part of this I wrote
a document that describes how they currently work, and some of the
3 matches
Mail list logo
