If the CA owner has not yet publicly disclosed an incident, they must notify chrome-root-program [at] google [dot] com and include an initial timeline for public disclosure. Chrome uses the information in the public disclosure as the basis for evaluating incidents.
If you have another instance of Chrome running and don't want to restart it, you can run the new instance under a separate user profile with the --user-data-dir option. Example: --user-data-dir=/tmp/chrome-debug. This is the same as using the userDataDir option in a launch-type config.
If you see errors with a location like chrome-error://chromewebdata/ in the error stack, these errors are not from the extension or from your app - they are usually a sign that Chrome was not able to load your app.
Using Ctrl+Shift+R to refresh was nice but didn't get everything I needed.still some things wouldn't refresh, such as data stored in js and css.found a solution: a toolbar of google for chrome web developers. After you install the toolbar select options and "reset page".
In actuality I want an option to completely disable the cache, to use the memory for IO instead of my disk (which would make load time 10x faster too!) but I don't think chrome or any browser for that matter has that option yet.
You can launch Chrome using the --test-third-party-cookie-phaseout command-line flag or from Chrome 118, enable chrome://flags/#test-third-party-cookie-phaseout. This will set Chrome to block third-party cookies and ensure that new functionality and mitigations are active in order to best simulate the state after the phase out.
You can also try browsing with third-party cookies blocked via chrome://settings/cookies, but be aware that the flag ensures the new and updated functionality is also enabled. Blocking third-party cookies is a good approach to detect issues, but not necessarily validate you have fixed them.
The problem is that since the latest chrome update, starting in version 109, the current tab is no longer available in selecting what to share when doing a screen share. I believe this is due to "selfBroserSurface" setting, where chrome now defaults to "exclude".