Browser: Google Chrome is up to date
Version 68.0.3440.42 (Official Build) beta (64-bit)
OS: MacOS 10.13.5
Running the official example from https://developers.google.com/youtube/iframe_api_reference observing a unusual bug.
note: Observed problem is a separate project, but replicated it with this canonical example.
Loading code from a local webserver running on port 8082:
npx http-server
note: Added console logs to the onPlayerStateChange function to assist in troubleshooting.
If run with dev tools NOT OPEN observe the bug. If run with dev tools OPEN do not observe the bug. Also, the bug does not appear to happen in latest version of Firefox.
Console Output with dev tools NOT open (until after) - BUG
Console Output with dev tools open - NO BUG
Ok... Believe the odd behavior with it working with Chrome Dev Tools open fooled me. Just happened to find a reference to a new Chrome Browser flag (and feature) that disables autoplay videos. The answer is to set the following flag on your browser:
chrome://flags/#autoplay-policy
Apparently, if you set the player with playerVars to be muted and it will also work too (verified myself).
Related
I'm using Microsoft edge(latest version-edge 100) and Dev Tools(F12 function key)
When I modified CSS Style on Dev Tools, Sometimes I can't save for override
This problem does occure on same website address include port number(for test experiment)
The port number address indicator :(Colon) seems to cause problems when copying to the local disk.
not save for override ex) XXX.XXX.XXX.XXX:80/~~~
Please solve the problem, Thank you
I tested the local override in both Chrome and Edge and although it failed in Edge (Canary 102) as you described, it worked fine for me in Chrome (latest Canary version: 103).
Because Edge and Chrome are both based on the Chromium open-source project, I expect the fix to come to Edge soon too (Edge gets updates from Chromium a little bit later than Chrome does, but it's usually a matter of days).
The bug pointed out by Yu Zhou seems to be the right one the fix from that bug will eventually come to Edge.
For information, the Edge DevTools team also listens for feedback on this GitHub repository: https://github.com/MicrosoftEdge/DevTools
I'm new in StackOverflow and I'm a beginner in web development thank advance for your comprehension.
I have problem with SASS
it tells me well in my terminal that it compiles my code on my main.css but this shows me the result only a few times on my browser (Firefox and I cleaned his caches).
I use the terminal of VSCode (Windows Powershell) I have SASS with node.js and local server with WAMP.
I find it hard to understand my other projects I did not have this problem.
Know what I can do to fix this?
You can find my code on GitHub and a video to show you the problem.
Thank you and have a good day!
Code of my project on GitHub: https://github.com/ValentinBnmr/Semaine_Inter
Video:https://youtu.be/dV_FcwNwwcY
PS: Sorry for my poor English.
First of all, check if the value actually changes within the compiled css file. Since your Sass compiler tells you that it compiled everything successfully, it should then be changed within your css file.
It is most likely your browser's cache. Clearing it once has no effect on later reloads as seen in your video. You can set your browser (both Firefox and Chrome) to deactivate Cache while developer tools are open.
Chrome: open DevTools [Ctrl Shift i], open its settings (either hit [F1] or open via DevTools menu), under "Network" check the box at "Disable cache (while DevTools is open)
Firefox: open Web Developer toolbox [Ctrl Shift i], open its settings (same with Chrome), under "Advanced Settings" check the box at "Disable HTTP Cache (when toolbox is open)"
Whenever you load a site with those tools open (as it should be when doing stuff like this) you will never run into cache issues anymore.
I have website which contains SCORM package, installed on Windows Server 2012 R2 which has IE11 installed on it. Flash Player is also embedded with IE.
IE Version: 11.0.9600.17278.
Updated Version: 11.0.12 (KB2977629)
When I launch SCORM (flash Player Content) from my application, it is not working. It just displays a blank page however the Title of IE is set to the text from the SCORM content.
However if I access the same URL from any other machine which has previous version of Windows OS (i.e. previous to Windows 8 OS), it is working as expected on IE9, IE10 and IE11.
While trying to find out the cause, I came across some forum which says we have to install the “Desktop Experience” on the server to enable the inbuilt flash player. After doing that also, My SCORM contents are not getting displayed.
To find out more details, I have uploaded the SCORM Package on SCORM Cloud to check if it is working there. Here again the same problem, it doesn’t work and displays error message saying that “Member is not found” and when I tried to find out the location of the error then it is coming at windows.document.myflash.SetVariable(…) method on the Windows Server 2012 R2 with IE11.
When I performed “Addwatch”, it is saying that windows.document.myflash doesn’t have SetVariable(…) method.
However if access the same cloud URL from other machine (Having OS previous to Windows 8 OS), it is working as expected.
Any help would be appreciated.
Thanks.
Windows Server has probably a restricted Internet Explorer installed (this is an addon for IE that restricts the kind of content that can be run from a web page).
If this is disabling flash content, you will have to uninstall the addon.
You could check if any other flash based page is working, e.g. Youtube to confirm that Flash is disabled.
I found the cause and the solution for the same.
Actually it was throwing an javascript error which was expecting "StudentName" and "StudentID" property which I haven't set. However even though I was not setting these parameter, it was working on other versions of IE.
After setting these parameters, it is working now.
Thanks for all suggestions.
System info: Win 7 x64 SP 1, IE 10, Visual Studio 2010
I've been researching this error all over.
visual studio debug error:
"unable to start program (File path) no more files"
This started with the installation of internet explorer 10 and is happening across all my web projects within Visual Studio 2010.
I've tried all possible solutions (but not VS re-installs) from registry entries (http://forums.asp.net/t/1891930.aspx/1), IE 10 reinstall (fail...won't let me reinstall due to existing version) to switching default launch browser (in Visual Studio, select a different browser such as Chrome to be default browser in "Browse With..." option in project..it works but is pain in the rear) but one thing I just tried which is making me wonder if there is an issue with how IE 10 is launched came from the following experiment:
Basically I did the same process of changing the default browser except that I picked IE 10 x86 version manually in the "Browse With..." option, set it as default and ran project. Voila, it works with no issues.
My next step was to confirm the default IE option in the "Browse With...". I found articles such as (http://lennybacon.com/post/2010/08/22/rehowtochangethedefaultbrowserinvisualstudioprogrammatically) which put me on the path to find out where the settings are for Visual Studios default browser settings.
I checked the browser.xml file and all looked ok including the registry entry pointing to it. I'm unable to check the version of the browser since MS, in it's infinite wisdom decided not to show that info in the Help -> About or anywhere else. so my gut feeling is that the default IE 10 being launched is the x64 bit version.
Does anyone know?
1) how I can confirm the default version of IE 10 launched since afore methods have not worked and
2) why would (I'm assuming) IE 10 x64 launch vs. the defined IE 10 x86 referenced version in the browser.xml file?
Thanks for any and all help.
Dave
UPDATE:
So from doing continual testing, it seems that after I ran the process to change the Default Browser settings in both the registry and the browser.xml file, upon launching the debug process in Visual Studio 2010, it automatically reverted back to the original default broswer settings which would launch the x64 version of IE 10. So in my case, it seems that the issue (error above) lies in the fact that debugging in Visual Studio 2010 using x64 browsers would cause the error. With no recourse, I ended up removing IE 10 from Windows Features and going through a painful process of getting IE 9 back on my system, I now can effectively debug using IE (x86).
It seems that MS is not pursuing any fixes for this issue of the default browser in VS 2010 from what I've read. There are in browser tools I've seen to do the default browser setting changes but don't want to bother with it/don't trust it will work.
Hopfully this helps others dealing with the same pain I have endured...
Thanks
Dave
When I ran into this problem (using IE 11) I noticed that iexplore was open about a hundred times in the task manager. After killing them all I was able to open my project just fine.
Since then, I have made a .bat file with this code: taskkill /F /IM iexplore.exe /T
so now I just run the .bat when I get that error. (alternatively you could run that code from the cmd)
James Butler's response is good for killing all the open IE processes. Which seems to be the issue here. The best solution I have been using is to just set, "Don't open a page. Wait for a request from an external application." then I just refresh the URL (if already open in browser) each time I rerun the debugger.
Access in Project properties under the, "Web" option. Then change setting there.
Check the following registry key
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\TabProcGrowth
Make sure that the value is Minimum
I started getting this error today after restarting from a Windows Update. I'm on Windows 8.1 desktop using VS.NET 2013. To fix I had to add another browser choice in VS debug that was pointing to the x86 version of IE11, and set that as the default. Although the post alludes to the x64 vs x86 browsers being the issue, this seems like an easier solution than the original poster's process of uninstalling and reinstalling browsers.
This blog explains how to set the default browser for debugging to IE x86: http://weblogs.asp.net/gurusarkar/visual-studio-web-developer-express-starting-two-instances-of-internet-explorer-and-throwing-an-error
Have you tried this: "...try selecting the project node in Solution Explorer and choose Set as StartUp Project". Just worked for me.
https://social.msdn.microsoft.com/Forums/en-US/efd93f22-1f1f-4fb1-8ff3-e29104780572/unable-to-start-program-there-are-no-more-files?forum=lightswitchgeneral
I think this is caused by a more general issue of low available system memory. In my case, Performance Monitor showed I was using 82% of my available memory when I was receiving the error. Looking at the processes, the culprit for me was lots of Chrome processes. I shut down Chrome, which freed up about 2 GB of memory, and then I was able to run the debugger successfully. Shutting down lots of IE processes would achieve the same thing of freeing up lots of memory. So I think the solution is just to free up system memory by shutting down whatever processes you don't need open.
This is what is working for me with windows 11 and edge:
Project Start Options - Don't open a page. Wait for a request from an
external application.
Start - Local IIS (Microsoft Edge)/Script
debugging disabled
Create a shortcut to launch the application like
this: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"
http://localhost/MyApplication/
I'm trying to use the latest Google NaCl SDK. Following the instructions at https://developers.google.com/native-client/pepper18/devguide/tutorial
I downloaded the naclsdk tool from their site, ran update, and got a pepper_18 folder.
I set NACL_SDK_ROOT to the pepper_18 folder, went in to 'examples' and ran make. Everything seemed to compile just fine.
I started Chrome, looked in about: flags and about: plugins, and verified that NaCl is enabled. I installed the SDK Examples app (from: https://developers.google.com/native-client/pepper18/sdk/examples) and that works just fine.
Then I tried to run my locally built and hosted examples, going to http://localhost: 5301. The HTML loads fine but the NaCl content does not load. In the hello world examples, it says "Status: LOADING..." forever.
I double checked the HTTP server logs and I don't see any errors there. Is there another place I should be looking for logged errors?
Check for version mismatch
In Chrome navigate to about:version and check that the major version of Chrome is at least that of the Pepper version you used to build your examples.
Check the JavaScript console in Chrome for any errors
You can find it by clicking the wrench icon in the upper right-hand corner in Chrome and selecting Tools -> JavaScript Console.
Inspect the NaCl module for further information
In the JavaScript console, you can also inspect the embed element of the NaCl module. E.g., if the embed tag has id="nacl_module" you can inspect it by typing
theModule = document.getElementById('nacl_module');
theModule.lastError;
Check Chrome's output to stdout/stderr
On Mac or Linux start Chrome from the terminal and look at the output on the console. E.g., on the Mac, you'd typically go
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-nacl
On Windows, Chrome does not write to the terminal if started from a command prompt. For this reason you need to redirect stdout/stderr from Chrome by setting the environment variables NACLLOG, NACL_EXE_STDOUT, and NACL_EXE_STDERR. Point them to different files, e.g.,
NACLLOG = c:\my_project\nacl.log
NACL_EXE_STDOUT = c:\my_project\nacl_stdout.log
NACL_EXE_STDERR = c:\my_project\nacl_stderr.log
Then (re-)start Chrome (making sure these environment variables are in effect).
Connect a debugger
Instructions on using the debugging support (currently only 64-bit Windows and 64-bit Linux) are available at https://developers.google.com/native-client/pepper18/beta-docs/debugging.
Restarting Chrome means closing all windows
When developing for Native Client one often restarts Chrome. It is important to close all Chrome windows; otherwise it hasn't actually restarted.
I muddled through a few issues which I will document in case they help others:
Neglected to 'make' the examples (got a clue to make them from the asker's description).
Chrome would not let me run non-store chrome apps. Went to chrome://flags and enabled Native Client and Native Client GDB-based debugging.
The JavaScript console said the demo's nmf file under .../debug/ was missing. I changed the make config to build Debug instead of Release based on this.
Chrome console complained NativeClient: NaCl module load failed: ServiceRuntime: failed to start; NaCl's GDB debug stub requires --no-sandbox flag on Windows. See crbug…. Tried running Chrome from cmd with --no-sandbox. This results in an alert You are using an unsupported command-line flag: --nosandbox. Stability and security will suffer. The aforementioned error went away, but the examples still would not run - no UI.
Went back to chrome://flags and disabled Native Client GDB-based debugging.
Then most of the examples worked. The Google Drive demo complains Error: must be run as a packged app.
have you confirmed that you've run httpd.py from the examples folder? This script creates the localhost:5103 server that the apps can be ran from.
Also, what OS are you using?
~Main