Jake Archibald writes in his blog about the bigger problem presented by importing third-party content into web pages. Even CSS is a problem as a CSS keylogger demo showed the other day.
A few days ago there was a lot of chatter about a 'keylogger' built in CSS.
Some folks called for browsers to 'fix' it. Some folks dug a bit deeper and saw that it only affected sites built in React-like frameworks, and pointed the finger at React. But the real problem is thinking that third party content is 'safe'.
While most are acutely aware, yet ignore, the danger presentd by third-party javascript and javascript in general, most forget about CSS. Jake reminds us and walks through quite a few exampled of how CSS can be misused by third-parties exporting it.
Source : Third party CSS is not safe
(Score: 2) by maxwell demon on Thursday March 01 2018, @07:01AM (1 child)
There is no inherent reason why a toolbar should make your computer slow (unless you are low on memory). A well-designed toolbar should just sit there until you use it, without eating resources (other than the little that is needed to display it; but note that otherwise something else would be displayed at that place).
The Tao of math: The numbers you can count are not the real numbers.
(Score: 3, Touché) by MichaelDavidCrawford on Thursday March 01 2018, @07:37AM
I Rest My Case.
Yes I Have No Bananas. [gofundme.com]