Sometimes, Even the Best CSS Developers Build the Wrong Code

Not everything built by programmers is obviously useful. A recent piece of code set up by a CSS developer causes most browsers to crash. One user who tried out this pure CSS code experienced a crashed tab in Firefox and on Chromium on a Linux operating system. When the same user tested the code in Safari on an iOS device, it behaved like it was indefinitely loading.

Another user noted that Chrome states a new instance of the rending engine each time that you open a new tab to navigate to a site. In this type of a web browser, the CSS code will only crash the active tab. It will not cause a problem for any of the other tabs that you happen to have open.

A tester who tried Chrome in Linux Mint noted that the entire browser crashed, rather than just the active tab. Another user suggested trying a JavaScript while 1=1 on the console.log. This user's experience is that it is worse than a crashed tab. The tab hangs and does not close when a person clicks the "X" button to close the problematic tab. The result is a stuck browser in Chromium and Firefox. The delay causes the processor to work overtime trying to render the tab. This slows any other activity that your processor may be doing at the same time. To kill the tab entirely, go to Chrome, then tools, then task manager. It will close the tab even if the "X" button does not respond.

Several testers who use Macs noted that their browsers and tabs did not crash at all. This was for Mac desktop and laptop computers and not the iOS for the mobile devices produced by Apple. Overall, this CSS script opens up different attack targets in the different browsers, which is why it causes this wide variety of problems with closing the tab, crashing just the tab or crashing the entire browser. CSS developers are always looking for ways to learn, and this script is one way to test out how different browsers and versions handle CSS. For more information click here https://cras.sh/.