after several days with a lot of IE problem, i found out that the script does not work well in my Localhost.
Here's to replicate my issue:
download original bootstrap (with docs)
Run the docs on localhost, and upload the docs on 'online' server..
and i see several different layout, like no arrows on sub-menu, etc... but there's no problem with online docs
Any idea how to solve this problem ?
Check your paths? If images aren't showing it sounds like they're not in the right place. If your localhost isn't set up correctly using, for example, / to find the root might not take you where you expect to go. If you have Firebug try inspecting the element with that and seeing where it is looking for the image/styles/js and check your paths are correct.
If you still have IE8 please try to download:
https://github.com/twitter/bootstrap/zipball/master
and try to run docs/components.html in your IE8 local
Related
I have a live server extension in my VC and it works well, the problem is when I try to open my page without using the extension it shows up the page without any CSS colors or images or anything, I want to see my project with all CSS codes I wrote without using live server, thank you
Have your tried copying the full path of the file then entering it in the browser?
If that still doesn't work, try refresh the page when updating your html/css/js file.
Sharing your code will help us more to Debug it.
Instead, I suggest you,
Just recheck your internet connection if you're using any CDN or any API like Bootstrap, Tailwind CSS.
Check your links if referred to any external CSS or js.
In order to create a website, I first worked with MAMP in a local mode.
After finishing the index page, I uploaded it.
The problem is that the images on the website are bigger than in the localhost for the index page.
I inspected the elements, but the style applied to each div are same.
I used "px" as unit of length to display the images.
I don't understand why two elements styles can be different while their codes are same.
I think i know whats your problem.
It's a cache problem.
Delete your cache and check it out.
For developers there is a function called "Disable Cache" you can find it , for example, in Google Chrome here: https://www.technipages.com/google-chrome-how-to-completely-disable-cache
Edit:
Clear cache in Google Chrome: https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DDesktop&hl=en
I was working on some CSS code and then suddenly the server stopped reflecting any changed made on the server. At first I thought it was a caching problem but I disabled caching on my browser and even tried using different browsers but still it's using the old version of my CSS file.
If I download my CSS file from the server and open in the text editor, it shows all the changes I made to the code but they don't reflect on my website at all. The site is using old version of the CSS file that doesn't even exist anymore on the server.
What on Earth is happening with my server? Can it be a router caching problem?
I can't answer this but try to add in your html, where you include the css this: ?v1.
Example: src="resources/yourDir/style.css?v1"
This will force everything to download the new css.
You can add after the ? everything you want. Like a timestamp, just a number or words. Whatever you like.
Every other website I visit, the inspector works as expected:
But in many of the sites I'm editing within apache server (using xampp) somehow they doesn't show the "filename.css:lineNumber" data
Also, every change I try to do in the inspector in thse sites, doesn't do anything to the code shown in the source tab.
I've tried refreshing, hard refreshing with cache, closing and opening the tab, closing and opening chrome again. The same problem occurs.
In other sites the inspector works well, but not in many of the localhost sites.
Has someone experienced this before? Is there a way to fix this?
If you are using a client-side CSS generator library such as Lea Verou's excellent -prefix-free or client-side Less, you will not see source information as it has all been processed and reinjected as style elements.
Client-side Less has a property [dumpLineNumbers] to include source line info as a comment in the generated source. (I'm not sure if this will display in Chrome's inspector - but I think it might)
The only "fix" I know of for -prefix-free is to temporarily remove it, obtain the source info for reference, then put it back in.
I have had the exact same problem (not using a css generator), and it appears to be a known bug with the current version of Chrome, the solution is to use the more up to date Beta version known as Chrome Canary - Here's the link :)
https://www.google.co.uk/intl/en/chrome/browser/canary.html
Try to check what the format of your CSS file is. I had the same trouble with the UNIX and Macintosh formats. For example, try to open you CSS file in Notepad++ and in the bottom right corner of the window you'll see your current format. If you see UNIX or Macintosh there, click it with the right button of your mouse and change to DOS/Windows. Then save your file and refresh your page in Chrome. It definitely helped in my case.enter image description here
Hello so I was trying to include a sketch in my html page using the two lines below, but it didn't work:
<script src="processing-1.4.1.min.js"></script>
<canvas data-processing-sources="hello-web.pde"></canvas>
Of course I made sure to put all the files in the same directory. I already did some sketches that are working fine in Processing software downloaded from processing.org. So I basically followed the instructions here: http://processingjs.org/ and created a hello-web.pde file that contains the setup and draw functions. I keep hearing about web server but I don't really knowwhat to do? any suggestions please.
Processingjs doesn't work in chrome. Chrome has disabled some features which it requires. Try with Firefox!
If that's not the case, it could be something in ur pde file.
ProcessingJS on Chrome works fine for me.
First thing you need to do is:
create a local server using
Mamp
Set your root path.
run your HTML page like so:
localhost:myPort/myHMTLPage.html
(eg. localhost:8000/index.html)