Bing map v8 APIs cached in IE11 - internet-explorer-11

In my case, Bing MAP apis are cached in IE11. If I delete only bing map related js files in cache it works well.
If I run IE11 in always refresh from server debugging mode, it also work then.
Any idea why?

when I want to make sure the browser asks the server I add a version to my request. For example https://www.bing.com/api/maps/mapcontrol?bransch=experimental&v=1. Otherwise, chrome has a nice feature, in developer tools -> settings -> network you can check 'Disable cache (while...)'

Related

Working with multiple APIs for Multi-platform apps

I currently have a Chrome extension that uses Chrome's APIs and plan on making a Microsoft Edge version once it opens up as well. My question is how do you work with the multiple API's?
For example, I use the following to check if the extension has just been installed or not:
chrome.runtime.onInstalled
I'm assuming for Edge it would be something like:
edge.runtime.onInstalled
What's the best way to work with both of these? Do I just duplicate the code within the file where there is a copy of the code for one and the other and presumably the browser will ignore the other browser's code? (doesn't sound like the good option)
Or is there some cross-browser framework that I should use instead?
Or is there some other solution?
And please forgive me, this is my first entry into building extensions/apps, I'm generally just a Web Designer.
Thank you!
All browsers support or
chrome.runtime.onInstalled
or
browser.runtime.onInstalled
So, the right way is to start scripts in your extension with this code:
var browser = browser || chrome
And then use browser, for example:
browser.runtime.onInstalled
(I'm sorry about my english)
Edit:
Chrome and Opera support chrome and not browser.
Firefox support chrome and browser.
Edge support browser and I don't know if it support chrome.
Anyway, my solution work in all browsers.
Update (5.8.16):
Edge support browser and not chrome.

Create/embed Firefox/Chrome base browser in Visual Studio

Im creating a freeware application (long live the free community) and I'm trying to add various features that might drive people to use the application such as implementing whatsapp web https://web.whatsapp.com/ into the app so that the user will always have an "always on top" window with their chats rather than everytime having to switch tabs if they're multitasking on their browser.
The problem i am having is that the built in Browser control with VS 2013 does not work with whatsapp web and i get the option to use supported browsers like firefox...chrome...safari.
Is there anyway to make a VB.NET application open an actual chrome/firefox based browser within itself?
I found an article on Gecko Browser...I am not sure if web.whatsapp.com would see this as a firefox browser: http://www.vbforums.com/showthread.php?692005-Mozilla-Firefox-Gecko-Xulrunner-in-VB-NET-%28versions-14-and-up%29
Help appreciated.

Use the remote debugging protocol in the Chromium based Opera

I use the Google Chrome remote debugging protocol to get benchmarking information of the page loading process with Google Chrome. I would like to switch to Opera which should offer the same functionality now that it runs on Chromium.
I started Opera with the cli parameters "--remote-debugging-port=9222 --enable-benchmarking --enable-net-benchmarking" similar to starting Google Chrome. I discovered that benchmarking seams not to be started in Opera - the chrome.benchmarking object is not visible to JavaScript.
I didn't find any documentation on the cli parameters for Opera, neither how to work with the remote debugging protocol in Opera.
Does anybody know how benchmarking can be enabled and/or the remote debugging protocol works in Opera?
Maybe you don't need this anymore, but I did today.
For some reason (maybe it's by design, but I didn't bother to check), you can't really start two separate instances of Chropera. Therefore, you first have to exit opera (from the menu to save your session).
Then, find your installation directory, and start Opera with the params:
C:\PROGRA~2\OperaNew\31.0.1889.174>opera --remote-debugging-port=9222 "http://www.opera.com"
(Maybe you can use launcher.exe, but I didn't bother checking)
Then, using another browser, visit http://localhost:9222. Maybe you can use the same one, but again, I didn't bother checking.
Now it's just the same as the Chrom(e|ium) protocol.
Hope that helps somebody.

Is there any API to disable prerender feature in chrome?

Without using automation, is there any way to programmatically disable prerender feature (Advanced Setting: Predict network actions to improve page load performance) in google chrome?
I couldn't find any straight forward API that allows me to modify this setting. So, I tried modifying dns_prefetchin->enabled in the "[Chromedir]\User Data\Default\Preferences" file to "false". But that value was getting reset every time I open Chrome. Using the Procmon utility didn't provide me any additional clues on where chrome may store its settings.
Thanks in advance.
Edit: I should mention upfront that using command line option --prerender won't work as I need this value to be turned off for all instances of chrome (even when launched by Operating system shell).

How to create an auto updater for browser extensions/addons?

I need to create an auto-updater on clients computer that will automatically update
a particular addon on Internet Explorer, Firefox, ...
Of course user previously agrees that there will be automatic updates on his computer.
Do you guys have any idea where I could start to do this ?
I started thinking about running a process on the client side that with ask our
server every couple of hours if there is a new version and then do the necessary
update on the client side.
The idea is to update our addon on multiple browsers without prompting the user of a new version.
Is there any tools that you could recommend ? Thank you for the help.
Edit: I can use Firefox and Chrome 'updateURL' in the manifest. But how do I automatically update a BHO (IE extension), and a Safari extension ?
Firefox and Chrome have a built-in extension updater, an extension shouldn't bring its own. The updater works by periodically checking a particular URL for information on the current extension version. Firefox documentation: https://developer.mozilla.org/en/Install_Manifests#updateURL. Chrome documentation: http://code.google.com/chrome/extensions/autoupdate.html.