Is there a possible way to use Google Geolocation API without Google Gears???
The reason being:
1. I want to user to enjoy the function of My Location without having to install installer especially when the page has potential problem of downloading the Gears installer.
When I was trying to install Google Gears from GOOGLE CHROME, it shows me the following error on the page of http://gears.google.com/
"Gears for Windows
Your browser is not supported.
Please check the list of supported browsers below." <---Google Chrome version 14.0.794.0 which is quite latest dated 23rd June 2011
Here is my another question, how it it is possible that Google Chrome itself couldn't support their own website??? This is ridiculous. I can even download the installer with IE 8 compared to Google Chrome version 14.0.794.0
Use the W3C Geolocation API.
Gears is being discontinued by Google in favour of HTML5 so I suspect that's why they don't automatically include it with Chrome.
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)
We have recently enrolled onto Chrome's origin trial for the new WebCodecs API (formerly known as "MediaCodecs"). The origin trial is supposed to start in Chrome 86 (see https://www.chromestatus.com/features/5669293909868544).
Despite that, the corresponding Web APIs (eg., VideoDecoder) are not available in the Chrome beta (version 86) and development (version 87) releases. Does anyone know Google's policy as to when features behind an origin trial are actually made available to developers?
OK, found it. The WebCodecs API does not (yet?) appear under chrome://flags. However, it can be enabled when invoking Chrome on the command line (Chrome 86+ only). So on Linux, this is:
google-chrome-beta --enable-blink-features=WebCodecs
Other than that, when putting a site under the respective origin trial, the WebCodecs APIs (eg., VideoDecoder) are also automatically exposed.
According to https://www.chromestatus.com/features/schedule it's supposed to come to chrome 86 stable on October 19.
Chrome 88 can work out of box now :-)
An example:
WebCodecs MP4 extraction demo
NPAPI plugins are not supported on Microsoft's new browser Edge.
Google Chrome developed Chrome Native Messaging in order to interact with an executable installed on the computer provided its link on the registry (for Windows OS).
Firefox seems to want to support Chrome extensions in the future, and we can assume the browser will eventually support Chrome Native Messaging as well.
Internet Explorer will continue to support NPAPI until 2020 (from what I heard).
For Edge, no solution has yet been developed (or is there one?)
I'm willing to work with URL handlers (myapplication://mydata) in order to compensate for this lack. Is there a better approach so far?
https://msdn.microsoft.com/en-us/library/aa767914%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
My intent is to communicate through an HSM installed on the computer, and use the Crypto API interface, or a PKCS#11 driver in order to sign data and send back the result to the browser. With a chrome native messaging extension, it actually works well. With a URL Handler, I will be able to send data to the executable, but I won't get the result, so I will have to think to post the result to a web specific URL, but this can result in a security hole to my perspective.
Thanks in advance,
EDIT : 2017-01-14 : The following link shows the progress of the adaptation of the Microsoft Edge Extension API :
https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/api-support/extension-api-roadmap/
EDIT: as Beckyang posted recently, there is a link where you can vote for the feature to be developed in priority, here :
https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/13612338-native-messaging
After reading some recent news:
https://github.com/david-sabata/web-scrobbler/issues/678
http://www.theverge.com/2015/7/30/9072271/microsoft-windows-10-updates
http://news.softpedia.com/news/microsoft-wants-google-chrome-extensions-to-work-on-edge-with-zero-work-to-do-488282.shtml
It seems like the adaptation of the initial Chrome extension will be possible as soon as Microsoft has implemented a "Chrome-Extension-like" API. So, eventually, It won't be necessary to develop something completely new.
The Native APIs are supported in Windows 10 Insider Preview Build 15002.
Native messaging in Microsoft Edge.
Is there a way to detect where a chrome extension installation was referred from. In case you want to rebrand the extension based on where the user came from
Android Apps are capable of this using intent com.android.vending.INSTALL_REFERRER and a referrer=something querystring on their Google Play URL, but I've been unable to find anything similar for Chrome Extensions.
I can probably do a 80% solution with cookies and redirects but it would be nice if this worked as cleanly as in Android INSTALL_REFERRER
It seems that there is no referrer option for Chrome Extensions and it is not listed in the documentation. See the following link for the closest I've found.
https://developer.chrome.com/extensions/runtime#type-OnInstalledReason
A workaround for this would be to pull the data from Google Analytics using the API. Referrals are recorded in Google Analytics for my Chrome Extension:
My cloud application is programmed already.
Which gets loaded using https://example.com to Google Chrome, then Google Chrome is accessing to the local machine as https://192.168.1.27/
but for security Google Chrome fails because the certificates are self-certified inside the embedded box of 192.168.1.27 (which i cant change).
But i trust it my lan and this device 100%. How can i instruct Google Chrome to avoid this and allow straight access?
You cant as of Google Chrome stable version (13 May 2015)
Ask Chrome Team to fix it. Its not logical and should be treated as BUG. When a programmer trust his lan and his own robots. There is no logic involved Google chrome should still un-trust it (so Chrome Team should brain storm it and add the feature).