3 ms·
I got a chuckle out of Edward, the frontend person learning about differences between the renderer and the browser process, which at this point is laid out for
by rzzzt 4y ago
I got a chuckle out of Edward, the frontend person learning about differences between the renderer and the browser process, which at this point is laid out for everyone in Electron's documentation: https://www.electronjs.org/docs/latest/tutorial/process-model https://www.electronjs.org/docs/latest/tutorial/process-mode...
I was struggling with this as well the first time I wanted to look inside an Electron app.
(Also that the change stopped the fun for Googlers that had enrolled devices as well. Is that still true?)
- rav 4y agocrbug 462221 links to crbug 471738 [1] - in which they change it from a simple "is device enrolled?" check into something that can be controlled with some kind of policy (not sure about the specifics). I'm not a Googler but based on 462221#c18 [2] it seems like turning off the easter egg would lead to some small but significant pushback, so I'm guessing they have a way to set the policy (even if there's no UI for it in the Google Admin Console). [1] https://bugs.chromium.org/p/chromium/issues/detail?id=471738 https://bugs.chromium.org/p/chromium/issues/detail?id=471738 [2] https://bugs.chromium.org/p/chromium/issues/detail?id=462221#c18 https://bugs.chromium.org/p/chromium/issues/detail?id=462221...