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.
Related
Note: I'm using an M1 Apple Silicon MacBook
Not sure if this is linked:
So I was using Atom to do some CSS editing last night. When trying to close it, Atom wouldn't close and the computer actually crashed. The file wasn't saved anywhere and was just a throw away copy paste editing file.
Today I started up my computer and opened Google Chrome and everything is busted. I've attached some images, one showing what it looks like in the inspect window, with a giant red box around everything, this has not been added, this is what it looks like in my Chrome > Dev Tools. It seems like the CSS of Chrome has been damaged in some way? I'm not a very experienced programmer.
I tried to reinstall Chrome and delete all Chrome Application Support files but the issue remained.
Also checked the Dev Tools > More Tools > Changes window
Does anyone know how this is happening?
Fixed this with the following:
Deleting chrome from Applications and emptying bin
Did a search for all files with "Google" and deleted 3 remaining files named "Google".
Deleted the Google files found in Application Support
Ran an Avast scan (found nothing)
Did a full cache/history clear
When I call the pages of my Yii 2 web application in Firefox bootstrap.css and bootstrap.css.map gets loaded six times with each request. In Chrome and Opera this doesn't happen.
On Fedora 20 with Firefox 33.1 and Yii 2.0.1. Server is on the same machine: Apache 2.4.10 with PHP 5.5.18.
What could be the reason? I have also Phusion_Passenger 4.0.42 installed. Could this cause the problem (but only with Firefox?)?
This seems to has something to do with the web development tools of Firefox. With Firebug the file is loaded only once, like it should be, but only as long as the Network monitor (or is it called Network analysis in English? In German it is Netzwerkanalyse) of Firefox is not opened at the same time! As soon as the network monitor is opened too, Firebug shows the reloading of the same file as well.
I don't know if it is a bug or if it is a (required) side effect.
I've found this behavior with different Firefox instances (not only one like I've stated in the question comments first).
I just changed from a linux/apache2.0/php4 web server to a windows/iis7/php5 web server (I only post php versions since that was a significant change).
My css is working just fine on the linux one (http://66.119.8.165/flcunderconstruction.php) but it isn't working on the windows one (http://66.119.8.236/flcunderconstruction.php).
Now, the issue only seems to be applicable to internet explorer 8 (maybe older, but I'm not testing those). Firefox and internet explorer 9 work just fine.
I think I've ruled out php issues as I created a non-php version (http://66.119.8.236/flcunderconstruction.html) and the issue persists.
I'm assuming the problem is in the css (which is quite large and throws up a lot of validation errors). But since it only occurs on the windows server and with ie8, I'm hesitant to start whacking away at the code.
Any ideas?
JJ
The broken version stops loading when it hits /include/html5.js. You only see this on IE8 because later versions handle the HTML5 stuff just fine without the polyfill.
Missing: http://66.119.8.236/include/html5.js
Present: http://66.119.8.165/include/html5.js
To test this, press F12 to open up the Developer Tools. Switch your Browser Mode to IE8. Jump over to your Network tab and press "Start Capturing". Perform a hard refresh (CTRL+F5), and watch as the files begin loading in. You'll note the 404 when it gets to the HTML5 polyfill. (Image below)
Using Fiddler2, I set up and Auto Responder to automatically add the HTML5 file from my local machine in the place of your missing file. Refreshing the request resulted in the entire site loading as expected in IE8. Put your polyfill on the other server, and you should be set.
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
Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.