IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
Portal appears to be broken in Chrome
Ron Jones
post Mar 26 2012, 18:41
Post #1





Group: Members
Posts: 412
Joined: 9-August 07
From: Los Angeles
Member No.: 46048



The portal (landing page for hydrogenaudio.org) appears to be malfunctioning. It displays only the header, footer and the navigational breadcrumb:

Go to the top of the page
+Quote Post
tpijag
post Mar 26 2012, 18:42
Post #2





Group: Members
Posts: 2345
Joined: 19-May 08
Member No.: 53637



Fine here. Maybe clear your browser cache. Close and reload browser and page.
Go to the top of the page
+Quote Post
Ron Jones
post Mar 26 2012, 20:48
Post #3





Group: Members
Posts: 412
Joined: 9-August 07
From: Los Angeles
Member No.: 46048



Yeah, that's the first thing I did.

A closer look indicates that some of the HTML generated is malformed and may be causing issues within Chrome (but IE9 is fine):

CODE
<td class='row2''>


(That's two apostrophes, not one quotation mark. That's bad.)
Go to the top of the page
+Quote Post
kode54
post Mar 26 2012, 23:52
Post #4





Group: Admin
Posts: 4578
Joined: 15-December 02
Member No.: 4082



I fixed that single quote bug in the template, but I don't know what else it needs.

Apparently, the bug only affects Chrome dev channel or newer. Neither beta nor stable exhibit the issue.

I would like to fix the glaring validation failures on that portal code, and heck, the main template, but I don't even know where some of the template bits are stored. Like that meta description tag that isn't terminated like an XML tag should be. And then a link or two that contain raw ampersands instead of &amp;, but that should be easier to find.
Go to the top of the page
+Quote Post
Garf
post Mar 27 2012, 01:15
Post #5


Server Admin


Group: Admin
Posts: 4882
Joined: 24-September 01
Member No.: 13



The site's (X)HTML isn't 100% compliant but that shouldn't be the problem - Chrome's devtools have no problem parsing the structure. This is simply a bug in (the development version of) Chrome.

I fixed some of the issues kode54 pointed out. If you point out more, I can fix those too. But it doesn't help Chrome.

You can also use Firefox, Opera, or hell, even IE. They work.
Go to the top of the page
+Quote Post
GenjuroXL
post Mar 27 2012, 08:30
Post #6





Group: Members
Posts: 46
Joined: 8-May 02
Member No.: 1998



Seems to work in the 18.x branch of Chrome, only 19.x is broken.
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 25th July 2014 - 10:20