Just to let all know, since the other thread kinda got off-topic and baried, that the SLEUTH files now have two cases uploaded.

A short story is on it's way, I am awaiting editing from my wife on that.

And again...I still need more submissions.
As of right now...I'm riding on almost empty again.

You can submit either a blooper case
You can also submit a simple account (not naritive please) of a run that you would like for me to write up in short-story format as well.

Hope you guys enjoy!

(takes medication)

For some reason, I can't read any of the text other than the headline when I view the page using Firefox, but it works just fine in Internet Explorer. FYI, I guess.

"No, they're talking about what explosives to put in the damn cube!"

I've got to work that into a game sometime...

Funny, funny stuff.

yeah, firefox makes black text over black background. You can highlight the text to see it, though.

Yeah, I can't see it with Netscape 7.2 either, though I don't see anything wrong in the source file and can actually read the story there...

[edit] Same as Backgammon.

Thats some impressive simultaneous posting, there.

And yes, the problem I'm having is the same black text/black background thing as the others here have mentioned.

Yeah, the problem's with his CSS.

Stumps, when adding hex color tags to your CSS, you need to add the # symbol in front of it to make sure it works properly. So instead of color: ffffff you need to change it to color: #ffffff. Otherise quality browsers just look at you like you're a retard and ignore what you put in.

Yeah, I fixed it I think.

Tell me if you guyes are still having any problems.

It was in the Stylesheet and various little areas else where.
(I got lazy...IE doesn't care if you have clean code...my bad)

hmm...*wonders if hers is the short story, or if it just didn't qualify...or just got lost in the email*

Oh...and I'm trying to find an artist to work up small artwork for the cases and more glamorous work for the short stories.

If you guys happen to know anyone who's pretty damn talented, and might be interested, send them my way would ya?
(I've already posted at the SR-artwork group on yahoo)

[edit](Whizbang, I sent a PM to you about that...sorry about the mess up.)

Text is still black-on-black for me.

On what page?

The stories.

Black on Black in Safari, too.

Fuck designing/testing with IE.

I continue to have the problem on both the main page and the story pages

Same thing, black on black in the Case pages. Mozilla 1.6b. Had to select the text to read it.

The problem is that you're now adding quotation marks. Strip them out. As mentioned above, it should look like this: color: #efefef;

just downloaded firefox so I can test properly

I think the problem is code support.
I don't think that these other browsers support this code in a css

TD.1
{
padding-left:30;
padding-right:30;
padding-top:30;
padding-bottom:30;
color: "#efefef";
font-family: courier new, arial;
text-align: justify;
background-image:
url('http://www.exigine.com/sleuth/images/office02.jpg');
background-repeat:
no-repeat;
background-position:
center;
background-attachment:
fixed;
}

[edit]I removed the quotes

The original looked like this:
TD.1
{
padding-left:30;
padding-right:30;
padding-top:30;
padding-bottom:30;
color: #efefef;
font-family: courier new, arial;
text-align: justify;
background-image:
url('images/office02.jpg');
background-repeat:
no-repeat;
background-position:
center;
background-attachment:
fixed;
}

See above. You can also save a bit of bandwidth by getting rid of all four of those seperate padding codes and just using: padding: 30; I'd probably add a px count to it, too (ie, 30px;), but that's just me. You don't need the single quotes in the URL bit, either.

Oh screw it, try this on for size.

Also, anywhere in your code where you have &nbsp you should actually have  

The paragraph tag is a container tag - each paragraph should technically begin with an opening <p> tag and end with a closing </p> tag.

Did that Doc...no dice

Mozilla shows black on black as well.

Edward

Edit. Also I don’t like the popup new window for the case flies.

Edward

Bah.

That still doesn't work...this is driving me nuts.

Basically I've narrowed it down to saying one thing for sure.
It's not the style.css.
Reason: nothing in any of the TD.x codes are working.

This means that it's not being called properly.
I'm trying to find out why right now.

Ok folks...
I'm going to keep working on this problem as over half of you visiting the site use a browser other than IE.

Right now, I'm at an impass and I'm dead ass tired. It's 6am and I need sleep.
I'll get right on this first thing tomarrow.

I apologize.

I have a fixed version locally, although I fixed it simply by ripping the page down it's bare elements and re-building. I'll rebuild the entire thing and upload it somewhere for you to check out, Stumps.

Thanks...but...what the hell was I doing wrong?

*just couldn't sleep with a bad page on my mind*

I have a friend who figured out the problem and a fix about a week ago, but never told you because he was trying to find a way to say it that didn't sound like "I hate you and hope you die". I'll try to get his input over here.

You did, however, fix the problem with the links on the sidebar. Good on ye'.

~J

Case #1 was black on black with Firefox 1.0PR.

But then I loaded one of my own CSS sheets via WebDeveloper. God, this thing pays for itself.

Seems to work fine for me with IE.

Yep, we've known it worked fine with IE from the beginning. IE is essentially the problem.

~J

I guess that means I'm part of the problem and not part of the solution?

Positive in that it positively encourages the behavior.

Again, I don't think it *encourages* the behavior so much as simply allows it. And if we *all* used IE, we wouldnt have had any problem in the first place. Which, of course, is probably the reason said functionality exists... but thats beside the point. The point is that IE manages to perform functionally in situations where other options are not functional, and that is a good thing.

The last version of IE ever made for the Macintosh does not work with that code. Because IE for Windows works with that code, someone put a page up on the net that does not work properly with an entire OS, probably two. It allowed this, it enabled it. If the person had been testing with a browser that did not allow broken code, it would not have gotten uploaded.

That is why IE allowing broken code to work is bad, because we can't just all use IE when a page breaks.

More importantly, we shouldn't have to. Should we be expected to all have off-road capable vehicle in case a road hasn't been built or maintained properly?

~J

Once again, it's only a good thing in that it encourages (and it most certainly does encouarge it) the behavior. It retards people from learning proper coding practices by allowing them in the first place. It's the frelling Ebonics of the World Wide Web.

In effect its also no different from proprietary code. It encourages websites that only IE can view (by allowing code that shouldn't work at all, thus is no longer a baseline).

If you want to fool yourself into thinking that it's a good thing, fine. Just don't expect anyone with half a clue to agree.

Then feel free to go back to using Mosaic 1.0 if you like.

Just because it's famous does not make it correct.

Well, I could continue to argue the point, but it doesnt really matter. I, personally, also do not use IE anymore - I use Firefox. Its pretty goddamn incompetent to allow a jpeg to compromise your system. However, at the same time, it does piss me off every goddamn time I encounter a web page that doesnt load properly, and I would be overjoyed if they built functionality into Firefox that would allow it to read sloppily-coded pages properly, without sacrificing the enhanced security that was my reason for switching to it in the first place.

Continuing with the car analogy: no, you should not expect everyone to have an off-road vehicle to navigate city streets. However, building a car without any shocks because the roads *should* be pothole-free would not be considered a positive thing, and, well, is actually pretty stupid.

But I'm done derailing the thread. Good luck fixing the code, Stumps.

I feel your pain.

~J, zealot since 1987

So everyone can rest.

Adam re-did the page and made it work fine.
Then I compared it to mine to see what was different.

Most of it was harmless things that weren't involved in keeping the black on black problem.

That, however, Adam had solved as well.

Aparantly, only IE accepts numeric values as class names for CSS.

TD.3 won't work when called as <td class="3"> in any browser but IE.
TD.text will work when called as <td class="text"> in any browser.

It's about that simple. I use numbers all the time in my css because I like the easy organization to it, but it turns out that this very common practice on my part was why I couldn't figure out what was wrong.
It works fine now.

[edit]Oh, and btw. If anyone notices errors in any of my sites or pages, let me know. Don't be afraid of sounding like an ass. Even if you're rude, I'll still get the notice that somethings wrong. I'd rather know than think it's all fine.
Especially when 51% of you guys are using a browser other than IE. That's pretty important.[/edit]

One more problem: you've got an extra e in November

~J