Closed Bug 533273 Opened 15 years ago Closed 15 years ago

make the front page valid html5

Categories

(Camino Graveyard :: Product Site, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: phiw2, Assigned: samuel.sidler+old)

Details

http://validator.w3.org/check?uri=http%3A%2F%2Fcaminobrowser.org%2F&charset=(detect+automatically)&doctype=Inline&group=0&ss=1 * the border attribute on the logo image should be remove and add this to the stylesheet a img {border: none;} * <meta http-equiv="imagetoolbar" content="no" /> should be removed (that is an IE windoze thing, similar to the send to iTunes contextual menu in Safari) * The last 2 errors refer to the comment start and comment end in the inline js. Those comments existed for old browser that didn't know about js, some loong time ago - Netscape 2 or there about. My computer tells me we're nearly in 2010 now... :-) # <script type="text/javascript" charset="utf-8"> # <!-- # # displayProperMessage(); # # // --> # </script> (I haven't validated any other pages yet)
Actually, the last two errors seem to be about the inclusion of: charset="utf-8" If I remove that, it works fine. I'm 100% positive other pages are broken, but this is fine for now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #1) > Actually, the last two errors seem to be about the inclusion of: > > charset="utf-8" > > If I remove that, it works fine. I'm 100% positive other pages are broken, but > this is fine for now. I'm pretty sure doing that breaks something in one or more of the messages, since I recall adding that part because of that breakage.
That doesn't make sense... but moving the JS to its own file should help, since we can just save the file as UTF-8. Yes? I think so... That's bug 531766, which is on my short list.
I thought the complaint was about the UTF-8 on displayProperMessage();. Was it for something else (my kingdom for a bonsai? not really :P)?
You need to log in before you can comment on or make changes to this bug.