Vega seems to intend to compile away both ... and =>. This is not supported in IE11 browser. Anything can be fixed to support IE11 browser?
We are using in angular 7 projects but it fails on module load for IE.
As described in Vega's Supporting Internet Explorer page, Vega does not directly support Internet Explorer. However, you can use a transpiler like Babel as part of your application build process to transform the resulting code and target a wider range of browsers / platforms.
Related
I would like to embed a modern WebView2 component (Edge Chromium Browser Control) inside an old-style VBA UserForm.
I surmise that I would need the following installed on the system:
Edge Chromium Broswer
Webview2 SDK
While I have the Edge Chromium Browser installed I am unsure how to install the Webview2 SDK outside of the context of a specific Visual Studio Project. To use it in a VBA solution it needs to reference some sort of global system-wide file?
Then, apparently the type library which contains the functionality we need to embed the Edge browser is Windows.Web.winmd. I presume I would need to "reference" that in some way but I am not sure how...
The closest thing I have found to answering this question is the following set of dlls:
http://vbrichclient.com/#/en/Downloads.htm
I am trying to deploy a vue application. I have to use Firefox ESR as browser (45.4.0) but I get the following error: TypeError: Object.values is not a function. If I use a different browser it works fine.
Could anyone help me?
Thank you
Support for Object.values was introduced in Firefox 47.
Your browser is from 2015. That is hideously ancient in Internet terms. Upgrade it.
(If you really want to to get the Vue application to work, you'll need to set up a Polyfill for Object.values. There is one linked from the MDN page I linked to above. It should also be available in core-js which can be used with Babel in the transpiling step of your build process.)
Say I wanted to support IE11 (and sadly, I do), how would I go about making gatsby develop work on that poor old browser?
Right now, I get this message:
webpack-hot-middleware's client requires EventSource to work.
This polyfill looks promising, but that's as far as I've made it.
Any help?
P.S. Probably worth mentioning that I'm using Gatsby v 2.4.7
Looks like Gatsby doesn't support IE in development, only in production, so no polyfills will be added and IE will error when using gatsby develop.
https://www.gatsbyjs.org/packages/babel-preset-gatsby/
Can confirm on my project that running gatsby develop doesn't make it work for IE11, but using gatsby build does. When running gatsby develop, all I could see on IE11 is a blank page.
As per the documentation of Gatsby, You need to use babel 7.
Babel helps ensure the JavaScript you write works across different browsers (including older versions of Internet Explorer).
Reference:
Babel 7 (Gatsby)
Gatsby leverages Babel 7’s ability to automatically add polyfills for your target browsers.
Newer browsers support more JavaScript APIs than older browsers. For older versions, Gatsby (via Babel) automatically adds the minimum “polyfills” necessary for your code to work in those browsers.
If you start using a newer JavaScript API like [].includes that isn’t supported by some of your targeted browsers, you won’t have to worry about it breaking the older browsers as Babel will automatically add the needed polyfill core-js/modules/es7.array.includes.
Reference:
Browser Support
Right now, we're dealing with bugs in our web app that only seem to be occurring when IE10 is in Metro mode. When IE is run from the desktop the errors do not occur.
Questions:
When IE10 is in Metro mode, is it effectively a different browser version than when it's run from the desktop? Would this explain some of the behavioral differences we're seeing?
If it is a different version, is there a resource that explains the differences?
Specifically worried about rendering engine differences or JavaScript versions.
Yes, there are two different versions of IE10: Metro/Windows UI and the desktop version. Here is the official documentation from Microsoft that explains the similarities and differences: http://msdn.microsoft.com/library/ie/hh771832.aspx
I've got a simple application using WebKitGTK 1.6.0 that simply displays a webpage in a window.
When I browse a page using it that contains an Ogg/Theora video and HTML5 video element it appears this simple application is using some mozilla plugins and even xulrunner. Can somebody tell me why this is?
Here is a list of files open by the program using lsof.
I built WebKitGTK 1.6.0 and most of it's dependencies from source including gstreamer-0.10 and the gstreamer plugins. No where do I recall configuring WebKitGTK to using any mozilla plugins or xulrunner.
What might be causing the mozilla plugins, libtotem and xulrunner to be loaded? I provided the link to the files the application is using in hopes that it might provide a clue.
Lol, found the reason. I have FireFox, totem and totem-mozplugin installed on my system. Once I removed totem and totem-mozplugin, WebKitGTK used the appropriate Gstreamer plugins to render the video and audio.