lukeo05

This article was on the BBC earlier this year, when the "pingdemic" was happening in the UK: https://www.bbc.com/future/article/20210705-how-children-are...

Kids realised they could get time off school if they faked a positive LFT so were using soft drinks to create false positive.

How true – or widespread – it is, I have no idea.

I've not read the article, but this came into my inbox today, which you might be interested in. An in-depth look at Project CETI, a research effort that seeks to use AI to understand the vocalizations of sperm whales off the coast of Dominica.

https://www.nationalgeographic.com/animals/article/scientist...

This is only true for DOM components, e.g. an <input> component, which can't have a onWindowShow() method associated with it.

Customer components, e.g. an <MyInput> component that wraps a DOM <input> and provides custom onWindowShow() functionality are unaffected.

It seems to me that the update process is slightly more jarring on OS X than it is on Windows (though I haven't used the Windows version so I am just assuming). When I finish using Chrome on OS X I will close the last tab with Cmd + W, so Chrome is still open and therefore it won't be able to install the update next time I open a tab. On Windows I would close the last tab and the application exits completely – though it might take slightly longer to open Chrome each time, I will never really have to manually restart Chrome to get the update installed.