CSS lost upon refresh
Hi, I hope someone can help us -- we have an ecommerce website that depends on customers having a good user experience, but we have been having this problem that our developer for some reason, cannot solve for some reason.
Basically, if you refresh the page on the site, all of the css is lost, it won't pick it up. Usually, if you refresh again, it will be correct again. In IE8, even refreshing won't help, the css will not come back in.
Has anyone heard of anything like this?? The site is in ASP.NET and prob Ajax --
the worst case scenario is when the css menus just list all of the items in the dropdowns - at the top of the page. It looks HORRIBLE. This only happens sometimes, and other times it is ok.
I would really appreciate it if someone out there had some clue as to what is going on and why the css is not picked up every time. I am not sure if it is because it is calling the css securely, ie https... somebody in our company with a fancy title and making a ton of money no doubt originally screwed up the security certificates and then we had to change every image etc. to https. Not sure at all if this has anything to do with this annoying refresh/css issue.
Thanks in advance for any help you can give me. Thanks!
please provide alink to the page
It doesn't do it all the time, so hopefully if you look and refresh, you can see what it is doing. Thanks --
I don't think I've ever seen a web page with 881 errors on it before...
I would start with moving your DOCTYPE to being the first link of the page, and address the issue of missing character encoding and xmlns attribute. Maybe that'll do the trick, but I'd have a discussion with your developer about the 881 errors in the code....
What character encoding is missing, etc. - is it something specific?
Yes, for example inside your <head> section you should have something like:
Originally Posted by keltoid
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
what we have is
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
it is at the top now, but not in the head section per se, because there is master page info at the top like
<%@ Master Language="VB" CodeFile="pc_master.master.vb" Inherits="pc_master" %>
<%@ Register Src="~/common/wsp.ascx" TagName="wsp" TagPrefix="uc1" %>
and more. I have moved the doc type to the top and it is up there now. The errors are things like 'no such attribute 'cellpadding' etc... is this some confusion with having an xhtml1 in doc type and having html??
I don't understand why having attributes like cellpadding is a problem and says there are issues with the ul and li ....
thanks for your help
I think perhaps there's some confusion about the doctype. Fundamentally you can think of the doctype statement as describing the *language* you're writing the rest of the page in. Let's say you were going to write a Word document, and had two options, to write in French or in English. Then you had a header (doctype) that stated whether the following text was going to be in French or in English. You wouldn't be asking "should my doctype say this is French or should it say it is English?" - you would know because that's the language you've written in. So to get back to the web page, it looks like you're writing partially in HTML Transitional, and partly in XHTML (by randomly adding closing slashes at the end of some lines), and you're now wondering what language to tell the parser you've written in. The answer is "none of the above" (or maybe "Franglish" :) ).
You picked XHTML Transitional, so that's the language the validator and web browsers are trying to parse.
Attributes like 'cellPadding' are illegal because all attributes in XHTML must be lowercase and you've got an uppercase "P" in there. In HTML you could mix & match case as you're doing.
Hope that helps,
Dave, thanks -- Yeah, I figure the same thing you figure - lol -- however, I have deferred to the developers who built the core of the site in asp.net. So maybe if I mention it to them, they will know which doctype they should use... its interesting that when I designed the new site it was primarily with css, yet one of their people reworked it all over in html, or a lot more of it. I was surprised, but figured it didn't matter. It really hasn't, but now we have this problem...
Thanks - I guess I can at least go through and take out all the capital P's and such. Not sure if we'll ever get rid of all of those errors. :D
edit: actually, can't make them with no capitals. It doesn't render the cell padding and spacing if I make them lower case....