When starting Chrome from a console, you can specify several options (e.g. --headless). Where are all the possible options listed? The official Chromium page (quite incredibly) links to someone's blog from 2013.
Is this still accurate? Is there official documentations?
Related
So I know Chrome has a feature to copy something on your computer (MacBook in my case), en then past it on your android phone. It looks like this:
This article explains to activate the feature by enabling the following experimental flags:
- Enable receiver device to handle shared clipboard feature
- Enable shared clipboard feature signals to be handled
- Sync Clipboard Service
Except I don't see these flags.
How can I still enjoy this functionality?
Chrome for Windows\Mac\Linux had a "share clipboard" feature until August 2021, when the Clipboard feature for non-ChromeOS devices was abandoned for security reasons as best I can tell, but being re-written from the ground up with "pickling" as the way to do it:
https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#pickling-for-async-clipboard-api
https://groups.google.com/a/chromium.org/g/mac-reviews/c/YPNrRBjGGbA
https://groups.google.com/a/chromium.org/g/blink-dev/c/Lo7WBM_v_LY/m/LncCKkXeAwAJ
Sadly those 3 flags are gone until they finish this rebuild of the cross-device copy\paste clipboard:
#shared-clipboard-receiver
#shared-clipboard-ui
#shared-clipboard-service
Here is a screenshot showing the Shared Clipboard flags until August 2021.
Many websites have not yet removed this from their guides.
You're not going crazy, I really miss it right now as I use Chrome cross-device on a Chromebook, Android, Macbook, and Windows PC.
Thanks #Michal for all the work to find some of this. I found some updated \ related links about some of the re-development work going into all this that #Herman may also find useful.
How to Use Clipboard Sharing on Google Chrome - (Outdated information now)
Then Nearby Share and other info:
Google is bringing Nearby Share and Fast Pair to Windows PCs (Jan. 5th 2022) (9to5Google.com)
Google Chrome for Windows is getting its own ‘Sharing Hub’ (May 12, 2021) (WindowsLatest.com)
How to use the share button in Google Chrome on desktop and Android (Dec. 9th 2021) (9to5Google.com)
Older item on 'Nearby Share' first showing up as a cross-platform item in all Chrome versions, even temporarily MacOS: Nearby Sharing is coming to Chrome on Windows 10 (July 31, 2020) (Techdows.com)
There is also some other news on sharing files that may be more ChromeOS related that has Chrome git links included here:
Google wants to make file transfers on Chrome OS much easier with 'Self Share' (19 Jan 2022) (AndroidCentral.com)
Chromium Gerrit - [Nearby] [Self Share] Add feature flag for Self Share
Google is working on a nifty new Self Share feature for Chrome OS
(January 2022) (Android Police)
So I have been following the following step for past few months:
Log in to Google Cloud Console from Chrome's incognito mode
Activate Cloud Shell
From there, I usually opened Editor and managed my files in a new window
Today while I was following the above steps, this issue raised up:
Basically, I cannot open editor anymore. I have already went through similar posts, and my issue is that I am using incognito where browser extensions or cookies shouldn't be an issue.
I am facing this problem for the first time and if anyone knows what is the cause or any suggestions would be appreciated.
EDIT:
For now Microsoft Edge InPrivate Mode is working for me. I am still interested in fixing the issue for Chrome.
Have reported the issue in Issue Tracker. Please "start" for more attention.
This started happening recently because third-party cookies stopped being supported in Incognito mode as of Chrome 83. Third-party cookies are required for the editor to work because of the way the open-source Theia IDE is integrated into Cloud Shell. The team is exploring various fixes, but in the mean time the following workaround should work:
In Incognito Mode, click on the crossed out 'eye' icon on the address bar.
Click on 'Site not working?'
Click on 'Allow cookies'
Safari problem stems from the same issue, but I am not certain if a similar workaround exists.
I've encountered the same issue myself (I tried this on Chrome running on both ChromeOS and MacOS) - it looks like a bug so in this case I'd recommend reporting it on Google's Issuetracker (you can even put a link to this post).
UNfortunately it looks like it's not just the Chrome browser. I tried this on Safari 13.1 and found the issue you described is also present.
I didn't check other browsers but IssueTracker is the way to go. And be patient :)
I have written a simple Chrome extension and tested it using developer mode to load the unpacked extension. It works as expected this way.
Because the extension uses storage.sync API, I would like to undertake further testing with installations of the extension as published in the Chrome Web Store.
The Developer Dashboard for Chrome Web Store provides an option to publish to trusted users only:
Only trusted testers from your developer dashboard can see it.
You can also include members of a Google Group that you own or manage.
When I publish this way the trusted testers listed for my dashboard can reach the extension and install it from the Chrome Web Store. However, the extension is always disabled upon starting Chrome:
This extension is not listed in the Chrome Web Store and may have been added without your knowledge. Learn more
We, my testers and I, have not been able to find any way to enable an extension disabled by Chrome. Is there one? If not, the entire exercise of an "unlisted" publication mode for testing seems pointless.
The only work around I've found to this situation so far is to set the extension to "unlisted" rather than "published to testers" from the Chrome developer dashboard.
This is not at all satisfying, but did allow some real world testing in an unobtrusive way.
We have a Google Sheets Add-On that creates PDF (on an external server).
Our current Add-On is based on the now deprecated ui interface.
We would like to switch to IFRAME mode.
One problem is, that IFRAME mode disables PDF display in secondary windows (created form the sidebar) on Google Chrome (it allows them with Firefox).
The other problem is, that the user is not able to print from secondary windows on Chrome. (This prevents us from using pdf.js for PDF display, because printing is still impossible).
Is there a chance to enable allow-popups-to-escape-sandbox in IFRAME mode.
This would atleast solve our problems for Google Chrome on Windows (not on Mac).
I believe developers cannot set sandbox flags. This is set by Google. Good news is that starting today (September 16, 2015) I noticed that the flag allow-popups-to-escape-sandbox is being added to the HtmlService.SandboxMode.IFRAME
When my add-on opens up the desktop chrome browser is throwing an error Error while parsing the 'sandbox' attribute: 'allow-popups-to-escape-sandbox' is an invalid sandbox flag. right now. I have the latest stable version Version 45.0.2454.93 m
This error should go away with release 46 as per the documentation I can see online. If you wanted you could download the beta version (46) or dev version (47) to test it out. I wouldn't recommend deploying beta/dev for anything other than testing/development. Please note the compatibility risk with other browsers.
I want to run multiple Google Chrome application windows logged into the same web site (Twitter.com, say), each with different credentials. Is this possible? If so, how?
My initial testing shows that multiple Chrome app windows are not sufficiently isolated to do this. Logging into the second account logs me into the second account in both windows, suggesting that they are sharing information just as two Chrome tabs might.
You can use a Chrome "Incognito" window for this.
As you've found, Chrome windows are (like in most browsers) just groupings for tabs, not an authentication barrier.
look for a plugin called "swap my cookies"
You can't do that with chrome Incognito windows.
Take a look here: http://code.google.com/p/chromium/issues/detail?id=24690.
So that's right you can create only two isolated session: one incognito and one normal.
See the latest post:
Although it's an extension / plug-in and not in core Chromium, MultiLogin has been working quite well for me: https://chrome.google.com/webstore/detail/nccllfnllopfpcbjdgjdlfmomnfgnnbk
It can open new tabs, each with their own cookie jar.