Is it WebKit? Presto? Is V8 engine dedicated to Chrome alone?
WebKit and Presto are not Javascript engines, but rendering engines. Opera previously used a Javascript engine called "Carakan", but have since started transitioning from Presto and Carakan to Blink and V8.
As per wikipedia:
It remained in use until Opera 12.15, when the browser's developer Opera Software ASA began phasing Presto out of its products in favor of the WebKit layout engine and V8 JavaScript engine combined with a modified Chromium browser.
For more , you can go through Web specifications support in Opera Presto 2.12.
Related
is Spartacus 2.0 compatible with IE11 and Edge?
or can we have a list of compatible browsers with versions ?
thanks
Based on official documentation:
On the desktop, Spartacus supports Chrome with automated tests, and in general, Spartacus supports evergreen browsers. By default, Spartacus does not support IE11 because IE11 is missing certain modern browser features, such as support for CSS variables.
Spartacus supports browsers on mobile and tablet platforms as follows:
On iOS-based devices, Spartacus is tested with Safari and Chrome. Although other browsers are not tested, Spartacus should work with any iOS browser, because all iOS browsers use the Webkit-based iOS browser engine.
On Android-based devices, Spartacus is tested with Chrome, which is based on Chromium and the Blink layout engine. Any Android browser that uses the same engine will likely work with Spartacus. Other browsers using different browser engines are not tested, but those browsers that use Webkit should work as well.
You can find out more details here - https://sap.github.io/spartacus-docs/spartacus-faq/#which-browsers-does-spartacus-support.
But in practice:
You can support IE by self if you will not use #spartacus/styles library, cuz Angular fully supports IE 11.
My web extension works with Chromium browsers, Firefox, Edge, but as I understand - it is impossible now just to open the same codebase with Safari browser?
Update 2021
The Safari support for WebExtensions was released in 2021 and is available from Safari 14 (shipped with macOS Big Sur). WebExtensions for Safari are published in the App Store. Documentation here: https://developer.apple.com/documentation/safariservices/safari_web_extensions
Original answer
We cannot possibly know this for sure, but Apple is currently not planning to support (a version of) the WebExtensions API. The name of the standard/specification is Browser Extension.
Apple is not part of the W3C group which attempts to make a cross browser standard: https://www.w3.org/community/browserext/participants
For more general info on the Browser Extension W3C working group, see
https://browserext.github.io/browserext
The provisional spec can be found here: https://browserext.github.io/browserext/
In macOS Big Sur, Safari will support the WebExtensions API:
New support for the WebExtensions API and migration tools allows developers to bring Chrome extensions to Safari — letting you personalize your browsing experience with new Safari extensions from your favorite developers.
I would like to know how is chrome.storage.sync synced in Opera.
The documentations talks about Opera Sync, is that Opera Link?
Is there any web page to guide the users on how to enable the chrome.storage.sync extension settings sync?
Does Opera button>More tools>Synchronise have anything to do with it?
The Chrome Sync implementation is much more straightforward to me.
Can't use it if I don't know if it will work on Opera's side.
Unfortunately chrome.storage.sync is not supported yet. There is no any connection to the Opera Sync.
According to the Opera documentation at
https://dev.opera.com/extensions/declare-permissions/
chrome.storage.sync is not supported.
If you try using chrome.storage.sync in your code the browser will "fallback" to using chrome.storage.local to maintain compatibility, so it won't actually sync settings across multiple browsers.
What does Sencha 2 only work in Webkit browsers? I understand they require the Webkit engine, but why do they do this, what does this webkit engine have which the engines in Firefox / IE doesnt have? A browser consists of a HTML engine, CSS engine and Javascript engine - just for curriosity, is it the Javascript engine which is special with Webkit in respect of Sencha ?
When Sencha Touch started development, iphone, android and blackberry were the main platforms. All of them use a webkit based browser as default.
There were reasons told at that time like css transistions and image masking weren't supported by other browsers. I guess things might have improved now.
Size is also an issue. To support more browsers, more workarounds are required which increase the size of the framework.
From a business perspective, there isn't really a demand for supporting any other browser. If ie10 becomes big with Windows 8, they might support it as people have already asked about it their forums.
Someones already trying to make it work on Firfox. Here is the link.
Here are some posts from the forum
Post1, Post2
I am writing the Dojo applications. I want to provide the browser compatibility for Firefox 3.0+, IE 7+. Should I follow any specific techniques to get the browser compatiability?
The list of supported browsers is here : http://dojotoolkit.org/reference-guide/releasenotes/1.7.html.
One of the advantages of using a framework over plain javascript is that it deals with most compatibility issues for you.