Если вы закроете вкладку браузера , с которой работали в workspace, чтобы вновь начать работать с ней нужно сначала запустить DevTools, а потом загружать страницу с сайтом. Если вы сначала загрузите страницу, а потом запустите DevTools, то workspace работать не будет, пока вы не перезагрузите страницу в браузере.
And when I say "soon" (near the end there), I mean "cross-browser soon". View Transitions are currently supported in Chrome (MPA+SPA) and Safari (SPA). Firefox has started the work on their implementation.
What if I want to let my wife log into my account while I'm away? The devices need to be in close proximity right? I can't just tell her the 2FA code over phone like I can with authenticator apps.
V3 isn't about making things more secure for users, but LESS secure for users. All the security theater lets Google lock out competitors and ad blockers, while it doesn't really keep the few bad extensions from being worked around it. That's why there are eight times as many downvotes on this, as upvotes.
No, that’s just async fetch requests. This would be if you have a long, complex calculation somewhere in your code but you don’t want to freeze the whole page while it calculates
@7:45 Are any of these frame works on the way to redundancy in 2024? As a complete beginner which should one get into as a complete beginner? Any opinions?
It's ironic that Google gets its money, and three letter agency support, by violating our privacy constantly for its own benefit...but is making it harder for extension developers to access information we legitimately need, so they can force ads on us. It's similar to their hypocritical thuggery with Android.
Of course the real reason the corrupt thugs at Google changed the manifest was to censor the power to skip ads. In reality, they didn't even make them safer, because there are workarounds for all of the "security". It was security theater, masking the ad skip censorship.
good thing, but where is auto replay button???? i playing clicker game. i cant use extensions, because of our office banned this options in our chrome...
I really enjoy the CSS Podcast. I also think it's great that you make it available on RU-vid, because as a result episodes are easy to share. Please continue doing so, despite all the comments on every episode, asking for visuals, videos etc. Sure, CSS is very visual, so a podcast can't give the full picture of a CSS topic. However, most information regarding concepts, intentions and even some gotchas of certain CSS features can be provided just fine through audio-only. It's refreshing to have at least a few sources that allow me to stay up to date regarding the web platform without looking at a screen.
@ColinFox, the moment they start adding visuals, like you requested, they should probably stop calling it a podcast. This series has been incredibly successful for years with this audio-only format, helping developers by providing the information they need while they can multitask (working, driving, watching kids, washing dishes, etc.). If listeners want to dive deeper or don’t understand something, they always include articles with each episode that break down the content in detail. Also, the main audience of this podcast is on platforms like Google Podcasts (now RU-vid Music), Spotify, and similar services, which is why there’s no visual element!
You can find documentation here: developer.chrome.com/docs/devtools/performance/overview#compare (expand the Advanced section) but basically this section allows you to map say localhost to your production origin to get the CrUX data.
More details here: developer.chrome.com/docs/devtools/performance/overview#expandable-1. Basically it allows you to map one URL to the CrUX URL so if using localhost for local development you might want to see the CrUX data for that site's production URL.
