Web Site Anomaly
4 Feb 2008 20:22:10 UTC
Topic 193489
(moderation:
Task breakdown pages are not rendering properly with Firefox 2.0.0.11 on either Windows or OS X.
Specifically, FF isn't rendering the proper color for the Time Reported/Deadline column entries. FF does render it correctly for the other projects I tested for this on though.
Curiously, IE 6 SP1 renders the page correctly on the Winboxes I tested. However, I didn't pursue it any further on OS X, since FF 2 is the most current browser I have available for the Mac platform I have.
Alinator
Web Site Anomaly
)
I'll test later... About out the door to school right now...
Hi! This is a known bug
)
Hi!
This is a known bug with the server side code. Actually the HTML generated by some BOINC pages is not 100% HTML Standards-compliant. IExplorer and earlier Versions of Firefox are a bit sloppy so they will still render as intended, but the newest Firefox versions are stricter and refusing to render the ill-defined color codes.
CU
Bikeman
RE: Actually the HTML
)
Some? I'd challenge you to find a valid page on Einstein@Home :)
RE: Hi! This is a known
)
Hmmmm...
Given that, another curious aspect is SAH (newer sever side build, IIRC) and Leiden (older) render correctly while EAH doesn't. As far as strict compliance goes, I don't think anyone on the planet is. :-)
In any event, not much of an issue, but it freaked me out when I took a quick look this morning and thought all my current tasks had crapped out at first glance! Not a great way to start the day before the first cup of coffee! ;-)
Alinator
RE: RE: Actually the HTML
)
Including the page you linked to (try the direct input validation method on it)! :-D
Alinator
I hope the web pages don't
)
I hope the web pages don't change too much, I read them with a scripted program. It doesn't take much of a change to throw off my script.
RE: I hope the web pages
)
What pages? There are a lot with XML versions you should be using instead.
RE: RE: Hi! This is a
)
SETI has the # symbol in front of the color code, while Einstein does not. The HTML 4.01 Transitional doctype requires the #. All that needs to be done is for Einstein's HTML generation to include a # in front of the color code...
Of course, I'm reading that is discouraged. Use styles instead...
...but just adding the # sign will make it work for that doctype...
Brian
RE: RE: RE: Actually
)
Not sure what you tried, but it shows valid XHTML 1.0 Strict for me... I guess either you missed something on copying the source or the parser had a burp...
RE: Not sure what you
)
Validating a workunit.php page says it's invalid.