Not directly a programming question but certainly one on developer productivity.
Like many developers I'm running the latest version of Firefox DeveloperEdition, to take advantage of all its various toolset, whilst trying to listen to Spotify to drown out the open plan office.
Whilst not the first time this has happened; Spotify crashes repeatedly with the WidevineCdm plugin being blamed as the culprit... this usually happens without any playback, but sometimes after a couple of seconds.
Usually "Help" page hints of fiddling with plugin settings as per usual aren't all that helpful.
I know that it'll likely resolve itself in a few days, but as a curious developer, I would like to know why it persistently breaks?
Unfortunately my fix to use Google chrome instead of Firefox :-(
This error just cropped up on Windows 7 ultra running Firefox to watch Netflix. (August 2019). Chrome worked OK as well as windows 10. For me i seemed to have found a solution (hopefully) After lots of digging and trying solution I have Netflix working OK by tuning Exploit Protection off in malware-bytes Premium .
Related
the problem I'll be describing might be caused by different reasons:
on linux opensuse leap 15.1 gnome (wayland) I can share e.g. mupdf but not evince or libreoffice in chromium jitsi session with screen share application window
another participant on windows tried to share a pdf document using microsoft office 365 and it seemed to show on his browser, but not on the other conference participants' browsers (one chromium on linux as in 1., the other firefox on windows), so he could not share his screen
I could not find any information on this topic using search machines. So I would appreciate if there is any answer on this out there in the community.
Looking forward to solving this ...
Cheers
JFM
PS: on the setup described in 1. also obs studio fails to screencast, maybe there is something related to this system setup causing this problem, some video driver setting e.g.?
This is probably related to Wayland, which has more restrictions than classic Gnome. Since you are having the same issue with OBS this sounds like this a classic Wayland permission issue.
I know they are working on implementing screen sharing support via pipewire but no idea how far this is.
You might try to switch back to Gnome on the X-Server until this is properly implemented.
I have been having problems with my Windows 10 (for example my localhost:8000). So I started looking for an answer, and it looks like the good old IIS is causing this issue, maybe because it's not enable in the turn Windows features on/off. SO in theory it should be a piece of cake right? Well when I click next I get the following message:
Windows couldn't complete the requested changes.
The function attempted to use a name that is reserved for use by another transaction. Error code: 0x80071A90
I read somewhere that it may be related to the .NET Framework, I have Framework 3.5 and 4.6 installed. I have tried all possible combinations, enable both of them, disable both, only one, everything! Not real information around regarding the Error code either.
Does it have something to do with the version of Windows that I have? Which is Windows Home. Is there any other way to make it work? Thank you in advance for your input.
As this is one of the first hits when you search for that error message posting solution here...
If you get this error when trying to "Turn Windows features on or off" in Windows 10 - make sure to disable Antivirus program.
Culprit for me was Avast.
To disable Avast right click on the icon in task-bar -> Avast shields control -> Disable until computer is restarted.
After Avast was disabled I had no problems with adding new features.
The company I work for is preparing for application testing in IE8. Previously we have been using IE6. Many of our web applications are written in .NET 1.0 and 1.1 with more recent apps written in 2.x and 3.x. I know IE8 has an IE7 compatibility mode and it says it has a quirks mode, but most of our apps were written for 6, which is not specifically mentioned. Compatibility is for 7, which had a compatibility for 6. I do not know if that is necessarily carried over to 8. In 6 quirks mode was to run 5.5 sites without a problem. With no deeper explanation on any of Microsoft's release notes does it mention quirks mode as 6 compliant or even 5.5, just a basis of what it is (specific DOCTYPEs or no DOCTYPEs).
If anyone could shed some light on how sites and apps designed for IE6 should run in IE8 would be greatly appreciated. If anyone else has made a similar move how smooth was the transition?
Thanks.
We made a similar switch in our company. We went from IE6 to IE8 across board, the only issues we noticed were related to styling. Now if you decide to upgrade your IIS server than that might cause some of your ASP apps to not work correctly.
The only thing you should notice is that you have ensured that your CSS will work correctly in IE8. You can install IE8 in your XP and see what will happen.
ASP.NET code is not important, Pay yout attation on HTML,CSS and JavaScript.
Quirks Mode has in principle not changed. IE8+ describes it as “IE5 document mode”. If your pages are still using Quirks Mode, then:
rendering should not change much;
oh dear. In 2010, really? That's sad.
IE is dragging along bugwards-compatibility for every version of IE since 5.5 except IE6. MS dropped IE6-standards-mode compatibility from IE7, then found the ensuing compatibility problems made it difficult to push people to upgrade to IE7 (and consequently depressed corporate sales of Vista). Since then they've made sure that each IE release has modes to simulate its predecessors, but it was too late to bring back IE6-standards-mode support.
This disastrous mess would never have happened if some idiot hadn't “integrated” the browser with the OS. If it weren't for that we could all just run the standalone IE versions we needed for the apps we needed.
And document rendering mode is only half the story. Getting the JavaScript to work consistently is often more of a problem, especially if the code was a dirty unreliable hack in the first place (which, in the case of webapps aimed at IE6, it often is). On the other hand, webapps that already worked on Firefox and other more standards-compliant browsers should work on IE8 with little to no change.
I have installed IE8 on my system. I usually test my application on this browser, but the problem arises when i got to know that the client is using IE7. Now how can i test my application on IE7?
One possible solution is to have dual booting on my system. So on version of Windows i can have IE7 and on another i can have IE8. But i really don't want to use this solution.
Another possible solution is to use PC Emulator [ Don't know what is this, just heard about these ]. Using which i can have multiple IE version simultaneously. Have you ever tried this solution? Please name any good FREE emulator.
Please let me know if there is any other better solution.
you can use
http://www.my-debugbar.com/wiki/IETester/HomePage
and here can you see all browser versions as picture
http://browsershots.org/
I got the solution. :)
In IE8, click on Tools > Developer Tools | or press F12
Then in developer Tools > select the browser mode [ available: IE7, IE8, IE8 with compatibility view ]
This is what i was expecting. :)
Microsoft provides a free set of Windows Virtual PC images for testing various versions of IE on various Windows service packs.
Virtual PC is also free.
Have you ever seen Microsoft Expression Web tool? It contains kick-ass tool for testing pages in various versions of IE - SuperPreview. And this tool also available free, you can download it here.
It's much more easy to use it instead of Virtual PC images. But it can't replace VPC completely because testing in clear environment is also very important.
This is a quick and easy web service solution, good for quick testing.
http://www.browserstack.com/
For those who are still looking for an answer here's a Chrome extension
It has over 6 millions users, and it claims:
Top 10 Chrome extension since 2009!
-- WINDOWS ONLY -- WINDOWS ONLY --
IE Tab exactly emulates IE by using the IE rendering engine directly
within Chrome. This will enable you to use ActiveX controls and test
your web pages with different versions of IE (IE6, IE7, IE8, or IE9).
-- FEATURES --
Create a list of URLs that will automatically open in IE Tab
Group Policy support for enterprise deployments
Securely use the old IE rendering engine
Edit Sharepoint documents instead of opening read-only
Use Java, Silverlight, and ActiveX in Chrome seamlessly
You can also look at Adobe BrowserLab:
http://browserlab.adobe.com
Microsoft has launched Modern.IE to help with this. Go here to download a test image for your preferred OS and visualization software.
http://www.modern.ie/en-us/virtualization-tools#downloads
This question already has answers here:
Closed 12 years ago.
Possible Duplicate:
Running Internet Explorer 6, Internet Explorer 7, and Internet Explorer 8 on the same machine
I recently started a new job and my lead is out sick. He assigned me a bug in our code that only affects Internet Explorer 6. The developer box I'm running is Windows Server 2003 with Internet Explorer 7, though.
How can I open the web page and debug it from my computer in Internet Explorer 6?
Install Virtual PC (now a free download) and one of the disk images from this page that provides you with a vanilla install of XP with the browser you want to test.
Use IETester.
Step 1: Virtual machines configured for each setup you want to test. Use VMWare or Parallels if you are on a Mac.
Step 2: Automate your functional tests with Selenium. You will never look back!
We do all of our IE6 testing on a VMWare machine that runs XP with IE6. Obviously takes a bit of setup time but worth it once it's done.
I've played with many of these ie6 options, and the best IMO is just to have a vmware install with an ie6 image in the long term.
In the short term, however, I've had the most success with IE Collection, but it is still somewhat buggy.
IES4Linux and IES4OSX work [sometimes] on their respective Operating Systems too.
Use Spoon (was Xenocode)... http://spoon.net/browsers/
It will let you startup any number of different browsers in a sandbox from within your browser.
The advantage:
You don't have to install any virtual machines.
You don't have to rely on apps like IE Tester and can instead use the actual browsers.
This obviously doesn't apply to your specific situation, but for anyone who is running Windows 7, a good option is to use XP Mode. The XPM image has IE6 installed and won't expire like the Internet Explorer Application Compatibility VPC images.
Once you've installed XP Mode, create a shortcut to IE in the XP Programs menu (so a shortcut is published to your Win 7 Start menu). You can then launch IE6 side-by-side with IE8 on your Win 7 desktop.
You can also use Microsoft's own Expression Web SuperPreview
Download page: http://www.microsoft.com/downloads/details.aspx?FamilyID=8e6ac106-525d-45d0-84db-dccff3fae677&displaylang=en
Further info: http://expression.microsoft.com/en-us/dd565874.aspx
Edit:
Sorry I didn't notice your "...and debug it..." statement in the original post. I think SuperPreview will just show a side-by-side visual comparison. If you need to debug javascript or anything like that, then I would use the virtualization methods mentioned above. (In practice I actually use virtualization for testing, but I figured I'd suggest something different.)
Multiple IE works great.