Welcome to Geeklog, Anonymous Monday, March 20 2023 @ 09:49 pm EDT

Comments for Testing the New Look

Testing the New Look | 5 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Looks excellent

Authored by: MLimburg on Thursday, September 13 2001 @ 02:38 am EDT

Excellent stuff ....

Okay Mac and Linux guys .. step up and add your 2cents worth. I suspect the quicksearch form element is NOT going to work with older Netscape/Linux browsers.

---
Friends help you move. Real friends help you move bodies.

Looks excellent

Authored by: Tane on Thursday, September 13 2001 @ 03:42 am EDT

I had a friend take this screenshot

http://www.zopegeeks.org/stuff/wrong.png

Possibly NS 4.77, but he is not sure (menu fonts are corrupted, so he can\'t read it!)

Looks excellent

Authored by: MLimburg on Thursday, September 13 2001 @ 03:57 am EDT

Okay!

I have a (cough) design workaround for the search text field
All v4.x Netscape browsers will have a hassle with the sytlesheet using pixel settings for fonts, will look into fooling NS4.x into precentage (or something) font settings
There is a possible problem with the html code for block boxes .. will check them out a bit.

---
Friends help you move. Real friends help you move bodies.

Looks excellent

Authored by: Anonymous (Anonymous User) on Thursday, September 13 2001 @ 09:50 am EDT

Too lazy to login, but this is rob from macosxhints.com. Looks very nice on OS X IE 5.1, but there's an issue with the "What's New" box header - it's not large enough at the default size:

IE 5.1 What's New screen

The size is perfect, the size is nice, and a very nice use of color. Using OmniWeb on OS X, it's s till nice looking, but there are a few more visual glitches:

OmniWeb What's New screen

However, I think this is due to OmniWeb problems m ore than HTML problems on the site.

BTW, there appear to be some lingering bugs with the HTML changes in comment blocks. It's inserting spaces and hard returns at the end of the input lines, from what it appears when you 'preview' a comment. Not sure if this happens in all browsers or not, but I couldn't wrap a paragraph tag over the input line break - Geeklog inserted a space between the angle bracket and the "p"; I had to put it on a new line to make it work. -rob.

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks