How is phantom handling the Manifest V3 chromium update? It seems that WASM will no longer be supported for extensions, and I was wondering how yall are planning to handle the change? I'm working on a related chrome extension project and have been hitting my head against a wall.
Basically, I've been working on a JS based web3 chrome extension, but significant portions of most libraries aren't going to be supported come the new year due to the manifest V3 update. I'm considering moving to mobile, but I'd rather not. I was wondering how Phantom's approaching the problem?
Thanks so much - huge fan!
Related
I'm currently migrating a chrome extension from manifest v2 to v3.
The extension uses Google ReCaptcha for some features. It works well with manifest v2.
But for manifest v3, remote code is not allowed anymore.
So I must bundle a specific version of Google ReCaptcha (for example) instead of just loading it from this.
So, my questions are:
Does it even work? If it works, is it risky?
Are there any better approaches for my use case?
I have been debating whether using polymer in my chrome extension is worth while.
Here is the scoop. (or should I say scope, haha bad programmer jokes)
My extension relies heavily on web components which have been available natively in chrome since the release of chrome 36
Now, if the browser statistics listed here are correct, then logically, there isn't much of a reason to polyfill web components since only a small percentage of chrome users use versions earlier than 36 (and lets face it, chances are they aren't using extensions).
What do you guys think? Are there any other reasons using polymer in this case which I fail to see?
I want to detect whether a browser supports the Ember.js library. If not, I will show users a message to let them download the latest version of their browser. How can I do that?
There is an answer to a similar question contributed by an Ember.js core team member.
In it, he states that the majority of the browsers on browserstack.com are supported, meaning they do thorough testing.
Rather than show the message based on a functionality test of the user's browser each time they load your application, I suggest you instead build a list of known incompatible browsers (anything older than what is on BrowserStack would be a good start) and expand it based on monitoring your access logs or reported issues from the likely minority users on unsupported browsers.
That "blacklist" approach would serve most efficient, as Ember.Js and other libraries like jQuery are usually designed to continually support all new browsers.
I'd like to start developing Google Chrome extension using node.js (since I've already written a "text-to-song" script in node.js, and I'd like to turn it into a Chrome extension.) What would be the most straightforward way of approaching this problem?
Actually it is. Look at this Developers Live-cast. This is something I've been looking for as well, and this would help you.
This brings your node applications bundled to your browser.
Here is the repo!
EDIT:
I've noticed that this old answer of mine keeps getting upvotes now and then (thank you all).
But nowadays I'm more an advocate of using web apps instead of bundling your application into many platforms like the chrome store or whatever.
You can check the google's post here and here indicating some directions.
In practice I advise for you to start building a progressive web app (PWA) with offline capabilities using service worker and progressive stuff.
There are plenty of resources around the web nowadays and you can offer a much richer application that may achieve a much broader audience if you do it the right way.
Thanks again, and good coding.
Simple answer is NO, unless you can find a way to install node.js with an extension using NPAPI.
Nodejs and a Google Chrome Extension do have a couple things in common i.e they both understand javascript and they both use the v8 javascript engine.
Google Chrome Extension
"Google Chrome Extensions are small software programs that can modify and enhance the functionality of the Chrome browser".
To develop a Google Chrome Extension you should write some javascript and or html/css.
Then you can run the extension in your browser.
If you wish for others to download your extension you will have to provide config.json file that describes you extension sets permissions etc.
Nodejs
"Node.js is a platform built on Google Chrome's JavaScript runtime for easily building fast, scalable network applications".
To develop applications in nodejs you write some javascript and or html/css for web applications.
If wish for others to use you application you start you nodejs server and listen for incoming requests.
Summary
Despite some of the similarities a Google Chrome Extension and Nodejs have nothing to with each other. You cannot use them together in some special way outside of the normal client/server communication.
You can use a WebPack (GitHub) or Browserify (see handbook) to build web-browser extension based on the node.js code.
With Browserify, to convert your code, you can simply run:
browserify node-code.js -o node-code-out.js
Read more:
Browserify vs Webpack.
Build a Chrome Extension with Preact and Webpack (see: Preact Chrome Extension Starter).
Hello I have this webiste www.liiklusinfo.ee and it's basically designed to work on web browsers, but is it possible to see that map on an Android mobile-phone? I can see that it is possible, because http://kraater.eu/en/map shows up on my android phone, but why isn't my website showing up? When I open the page, it states that I must get a new API code, but I have all the right API keys..
It's definitely due to the fact that you are using Maps API v2 instead of v3.
"http://maps.google.com/maps?file=api&v=2&hl=en&sensor=false&key=ABQIAAAAzrzbFLxHQWFbTQr9PqQ_HhRwAQ6CP1ccuJFaeFcXqlGX2NtZ2xQSe3YINEpjxiDi-m_GSubdYtbMEg">
V2 is causing some issues which is preventing v3 from loading. You may be able to find the route of those problems, but it would just be easier to switch to v3.
I would recommend reading this guide:
http://blogs.missouristate.edu/web/2010/05/12/google-maps-api-v3-developing-for-mobile-devices/
I'd suggest upgrading to the version 3 api, the tag line is V3: The Solution for Maps Applications for both the Desktop and Mobile Devices after all.
This should solve your problem. Moreover, i can see the map on the opera mini browser on my android just not the other.