“If the sanitization logic in DOMPurify is buggy, your application might still have a DOM XSS vulnerability. Trusted Types force you to process a value somehow, but don’t yet define what the exact processing rules are, and whether they are safe.” — this caution from web.dev makes me want to play around with TrustedTypes more and get a better understanding. - Source: dev.to / about 2 months ago

Before we start creating pages in our application, it's important to understand how Next.js renders content. The framework supports multiple rendering methods including server-side rendering (SSR), static site rendering (SSG), and client-side rendering (CSR). There are many pros and cons to each rendering method (too many to cover in this post) so if these concepts are new to you, Google’s web.dev site has a very... - Source: dev.to / 8 months ago

The lifecycle of an interaction. Source: web.dev. - Source: dev.to / 4 months ago

Probably not, it's the CSS used so far, so if there are elements you've not interacted with, that's an issue. This web.dev article gives some tools you can use https://web.dev/articles/extract-critical-css. Source: 6 months ago

I noticed the same for Google's site https://web.dev/ The last article pushed to the feed was "Changes to the web.dev infrastructure" few months ago https://web.dev/blog/webdev-migration The feed still there but with no updates https://web.dev/feed.xml and on the site you can see new articles published. Is sad that on a infrastructure revamp of a modern site, the RSS feed was left out of the features list (at... - Source: Hacker News / 6 months ago

I came across css scan and it looked really nice, but then I came across css scan pro which is extremely similar to it, except for having a monthly payment instead of a one-time. Has anyone ever used these tools before, can tell me which one is better? Source: over 1 year ago