“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 / 19 days 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 / 7 months ago
The lifecycle of an interaction. Source: web.dev. - Source: dev.to / 3 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: 5 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 / 5 months ago
> One of the downsides of switching over our beloved http://web.dev to Google's own DevSite CMS is that it doesn't offer RSS. - Source: Hacker News / 5 months ago
Upon testing on Firefox and Mi Browser, there was no triggering of the BeforeInstallPrompt event, as expected. However, I noticed that web.dev manages to display a prompt on these browsers, even though they theoretically lack support for the BeforeInstallPrompt event. Source: 5 months ago
Web.dev, maintained by Google, including posts by Chrome developers and their co-workers,. - Source: dev.to / 7 months ago
In a old web.dev articleI came across the word "Incremental (Re)Hydration" which is linked to a Glimmer.js-Blog post (also called "Incremental Rendering" there) confuses me. Is Incremental (Re)Hydration the same as Progressive (Re)Hydration? Reading the Glimmer-Blog article it seems so, but in the web.devarticle it seems to be something different. Source: 8 months ago
Web.dev newsletter - though it's not a weekly newsletter and it's only content from web.dev (though really high quality content). Source: 9 months ago
Just open up a text edi web developers are self-taught. a website. That's what I did. Some people like this: https://web.dev. Source: 10 months ago
Manual Accessibility Testing from web.dev is a great intro to manual testing in general. Source: 11 months ago
I think web.dev is a good resource for doing this "correctly". But when in down, google if there is a more accessible way to implement some feature. Be skeptical of any code you get online, and question if there's a more accessible way to do it. Source: 11 months ago
I've going hard on trying to speed up my stores speed by myself because I don't have the funds to pay someone and so far I have done a lot of good work. However, there's one part that I can't figure out "Eliminate Render Blocking Resources" mainly to do with Themes.scss.css & J.query2.2.3.min.js, So page speed web.dev suggested that I try and remove non critical JS/styles, now I'm just a little stumped on whats... Source: 12 months ago
Check for core web vitals. Go to web.dev to check performance of your website. Source: about 1 year ago
Learning: If you are interested in frontend, start with HTML, CSS and JS. There are a lot of resources out there, freecodecamp, web.dev, theodinproject, mdn docs(developer.mozilla.org) and others. Pick one and get started. There are many more things that you will understand with time like frameworks (start with React for now) and other bits. Source: about 1 year ago
Chunks of data being sent over time make up what’s called a “stream“. Streams are kind of hard to understand the first time around, at least for me. They deserve a full article (or many) on their own, so I’ll share web.dev’s excellent guide in case you want to learn more. - Source: dev.to / about 1 year ago
Just ran Google.com through web.dev page speed and it failed core web vitals assessment. Funny that. Source: about 1 year ago
Google is your friend on best practices. https://web.dev. Source: over 1 year ago
That is nice! Only issue with using web.dev is they commonly put Chrome only features in their tutorials. Source: over 1 year ago
This is great. Though if you want to go the extra-mile, Google's https://web.dev/ (previously "Google Developers") is similarly the closest you can get to "front-end theory". It covers more advanced topics related to performance, how the render pipeline works, and patterns for architecting front end applications with scalability and performance in mind. Source: over 1 year ago
Do you know an article comparing Web.dev by Google to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Web.dev by Google. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.