browser

Permalink 1 user found helpful
Is there a difference between browsers to watch your website in and witch one is the best for a concrete5 website?

jackbasting
 
DAkers replied on at Permalink Best Answer Reply
Its usually good practice as a web designer to look at your website in every type of browser (i.e IE, Firefox, Chrome, Safari Etc.) and see if there are any issues regarding each one. Internet Explorer 8 usually gives the worst issues with cross-browser compatibility. Unfortunately a lot of my visitors still use that monstrosity.

You just never know what browser visitors to your site will use. You don't want a completely broken site on any browser.
Robmr replied on at Permalink Reply
Thanks for threads like this. This is just where I am at re building my site at present - I've looked at it across a number of browser platforms and some handle it better than others. (I also used a site called "Screen shots")

I'm very new to website development, how best can I go about avoiding major problems in addressing this issue please? Should I get a professional coder for a few hours to improve in the back-end, so as to to handle better handle different browsers, or, is there software or a plug-in that can help?

Sorry if any of this sounds crazy, but as I say I'm new to all this and will thankfully welcome any suggestions?? Thank you.
jackbasting replied on at Permalink Reply
jackbasting
Tanks for your answer DAkers.

And why it is possible that some changes you make not directly change in your browser?
For example: I changed the "header logo link" lettertype and letterhight. And i saw the chages I made only the next day.
JohntheFish replied on at Permalink Reply
JohntheFish
Many web files get cached by the browser. Chrome in particular has a particularly sticky browser cache.

If you refresh the page a few times (F5 and CTL+F5), the revised styles will be loaded.
jackbasting replied on at Permalink Reply
jackbasting
Thanks,

Indeed, it was Chrome where I was talking about.
Qantas94Heavy replied on at Permalink Reply
Of course check your concrete5 settings - you'll need to disable caching on the server end and also clear your cache when applying changes in your browser.