Re: [WSG] Announcing GrayBit v0.5 Beta

[Keryx webb]

Mike at Green-Beast.com wrote:

Russ, Steve,

Thank you. 


Mike Cherim
http://green-beast.com/
http://accessites.org/
http://graybit.com/


Hmm. I tried one of my sites, but except for the index-page, it does not pick up 
my CSS-file.


See http://graybit.com/files/graybit.php?url=http%3A%2F%2Fpenilla.nu
And 
http://graybit.com/files/graybit.php?url=http%3A%2F%2Fpenilla.nu%2Fcolophon.php

Also, my site uses iso-8859-1. Graybit sends it back as UTF-8, with predictable 
results for my Swedish letters, å, ä and ö.


Lars Gunther

**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Thierry Koblentz]

Mike at Green-Beast.com wrote:
> I made all of the suggested changes to the GrayBit [1]
> page/application -- downgrading to XHTML 1.0 Strict and correcting
> the font-size issue for IE (bugs passed along and added to the bug
> list) and I thank you for this. However, since I didn't hear from
> that many of you, I figured I'd continue this on one more time to
> solicit responses.

> Does an anyone have any additional feedback, good, bad, or otherwise?

Hi Mike,
I see two problems in IE 6:
- the main content jumps when the user hovers over the text box or over the
links in the footer
- the border of the text box decreases when the user hovers over it

I believe the padding value (in %) creates the first problem.
For the text box, my "theory" is that IE ignores the "button" class below
and wrongly uses this rule to style the text box hence the drop of 2px
(border top and bottom: 2px instead of 3px):
input.button.hover {blahblah} /* is read by IE as input.hover {} */

As a side note, since you have only one text box in there you can drop the
class and go for the element itself.

Nice tool, it doesn't do anything to my own site though ;)

HTH,
Thierry | www.TJKDesign.com

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Mike at Green-Beast.com]

Russ, Steve,

Thank you. 

Mike Cherim
http://green-beast.com/
http://accessites.org/
http://graybit.com/

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[russ - maxdesign]

> Is the submission form supposed to work? On both Firefox 1.5.0.1 and
> Safari 2.0.3 on Mac OS X 10.4.5 I end up with a blank screen when
> submitting my web site (dynamic using phpWebSite).
> 

Try adding "http://"; in front of the web address before submitting. If the
web address doesn't contain the "http://"; then it returns a blank screen -
at least for me.

Tip of the day: trim your replies! Saves people reading screens of text and
helps the environment (or so I have been told).

Russ


**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Steve Olive]

On 11/03/2006, at 8:41 AM, Mike at Green-Beast.com wrote:


Hello All,

I made all of the suggested changes to the GrayBit [1] page/ 
application --
downgrading to XHTML 1.0 Strict and correcting the font-size issue  
for IE
(bugs passed along and added to the bug list) and I thank you for  
this.
However, since I didn't hear from that many of you, I figured I'd  
continue

this on one more time to solicit responses.

Does an anyone have any additional feedback, good, bad, or otherwise?

Thank you.
Sincerely,
Mike Cherim
http://green-beast.com/
http://accessites.org/
http://graybit.com/ <<< [1]


PS. To anyone that missed my original posting, I have included it  
below:


- Original Message -

[...] "We just created a new tool and launched the beta interface  
[1]. It's

a
contrast accessibility tool of sorts, but different. It does some neat
stuff. The best way to understand it is to just try it.

Being it's in beta, we're keen on feedback. You can respond here or  
use our
form [2]. We do know that it doesn't handle PNG transparencies as  
well as it
could (in IE), and it will disable some site's javascripts (but  
still seems
to serve its purpose all the same). It works on sites using CSS  
(hex code

colors, color names, or RGB) but won't work well on older sites using
tags'n'tables. But then again the people who make sites like that  
probably

wouldn't have much interest in this anyway.

The interface is new for me in a couple of ways. It's my first  
"fluid" site
(I usually make fixed-width sites or jump right past fluid to  
elastic). It's

also the first site I made to the XHTML 1.1 DTD. I'm sending it as
application/xhtml+xml, but the browser is still processing the code as
text/html (give me comments on this, please). It's also my first  
PHP-only

site. I usually make PHP sites, but they have some PHP and some static
mark-up. These pages are pure PHP, dynamic. First thing on the page  
is and the last thing is ?>. Nary a break in between. You should find  
it very
accessible and very usable. I took three days on this interface  
crossing my

"t"s and dotting my "i"s." [...]

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**



Is the submission form supposed to work? On both Firefox 1.5.0.1 and  
Safari 2.0.3 on Mac OS X 10.4.5 I end up with a blank screen when  
submitting my web site (dynamic using phpWebSite).


The graybit.com page presented equally well in both Firefox and  
Safari - no differences or errors I could detect.


Steve Olive
Bathurst Computer Solutions
e-mail: [EMAIL PROTECTED]
Mobile: 0407 224 251
Web: www.bathurstcomputers.com.au
 _
... (0)>
... / /\
.. / / .)
.. V_/_
Linux Powered!




**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Mike at Green-Beast.com]

Hello All,

I made all of the suggested changes to the GrayBit [1] page/application --  
downgrading to XHTML 1.0 Strict and correcting the font-size issue for IE 
(bugs passed along and added to the bug list) and I thank you for this. 
However, since I didn't hear from that many of you, I figured I'd continue 
this on one more time to solicit responses.

Does an anyone have any additional feedback, good, bad, or otherwise?

Thank you.
Sincerely,
Mike Cherim
http://green-beast.com/
http://accessites.org/
http://graybit.com/ <<< [1]


PS. To anyone that missed my original posting, I have included it below:

- Original Message - 

[...] "We just created a new tool and launched the beta interface [1]. It's 
a
contrast accessibility tool of sorts, but different. It does some neat
stuff. The best way to understand it is to just try it.

Being it's in beta, we're keen on feedback. You can respond here or use our
form [2]. We do know that it doesn't handle PNG transparencies as well as it
could (in IE), and it will disable some site's javascripts (but still seems
to serve its purpose all the same). It works on sites using CSS (hex code
colors, color names, or RGB) but won't work well on older sites using
tags'n'tables. But then again the people who make sites like that probably
wouldn't have much interest in this anyway.

The interface is new for me in a couple of ways. It's my first "fluid" site
(I usually make fixed-width sites or jump right past fluid to elastic). It's
also the first site I made to the XHTML 1.1 DTD. I'm sending it as
application/xhtml+xml, but the browser is still processing the code as
text/html (give me comments on this, please). It's also my first PHP-only
site. I usually make PHP sites, but they have some PHP and some static
mark-up. These pages are pure PHP, dynamic. First thing on the page is . Nary a break in between. You should find it very
accessible and very usable. I took three days on this interface crossing my
"t"s and dotting my "i"s." [...]

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Gunlaug Sørtun]

Mike at Green-Beast.com wrote:

I didn't understand the "cut-off" thing you mentioned. I'm not seeing
 anything cut off. Could you elaborate, please.


It's that 'AD: Contact Us...' image.
Not much you can do about it, I guess.

Georg
--
http://www.gunlaug.no
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Mike at Green-Beast.com]

- Original Message - 

You've triggered the 'em font-resizing bug' in IE/win...

...by starting off with 'em' as unit.

Fluidity make fixed-width container look a bit "cut off" on that page,
on window-widths slightly narrower than 1000px.

MIME-type problems are best solved server-side.
That  doesn't matter much (or at all) to browsers once they
have been told to use a MIME-type by the server. Seems to be 'text/html'
alright.
However, 'application/xhtml+xml' won't do any good in IE anyway - since
IE/win doesn't understand what XHTML is all about. Better change that
DTD to XHTML 1.0 Strict, or change the whole thing to HTML 4.01 Strict,
and keep on serving your pages as 'text/html'.
More info...


regards
Georg
-- 
http://www.gunlaug.no
**

Thanks Georg,

I fixed the font-size thing. Oddly I usually set a percentage to start 
(100.1% usually). Don't know why I didn't do that this time. Good find.

I'll change the DTD to xhtml 1.0 strict later since there all I have to do 
is change the DTD. I actually have some script to generate that. All I have 
to do is adjust it.

I didn't understand the "cut-off" thing you mentioned. I'm not seeing 
anything cut off. Could you elaborate, please.

Thanks for the great feedback.

Sincerely,
Mike Cherim 

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**

Re: [WSG] Announcing GrayBit v0.5 Beta

[Gunlaug Sørtun]

Mike at Green-Beast.com wrote:


We just created a new tool and launched the beta interface [1].


The interface is new for me in a couple of ways. It's my first 
"fluid" site (I usually make fixed-width sites or jump right past 
fluid to elastic). It's also the first site I made to the XHTML 1.1 
DTD. I'm sending it as application/xhtml+xml, but the browser is 
still processing the code as text/html (give me comments on this, 
please).


[1] http://graybit.com


You've triggered the 'em font-resizing bug' in IE/win...

...by starting off with 'em' as unit.

Fluidity make fixed-width container look a bit "cut off" on that page,
on window-widths slightly narrower than 1000px.

MIME-type problems are best solved server-side.
That  doesn't matter much (or at all) to browsers once they
have been told to use a MIME-type by the server. Seems to be 'text/html'
alright.
However, 'application/xhtml+xml' won't do any good in IE anyway - since
IE/win doesn't understand what XHTML is all about. Better change that
DTD to XHTML 1.0 Strict, or change the whole thing to HTML 4.01 Strict,
and keep on serving your pages as 'text/html'.
More info...


regards
Georg
--
http://www.gunlaug.no
**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**

[WSG] Announcing GrayBit v0.5 Beta

[Mike at Green-Beast.com]

Hey gang,

We just created a new tool and launched the beta interface [1]. It's a 
contrast accessibility tool of sorts, but different. It does some neat 
stuff. The best way to understand it is to just try it.

Being it's in beta, we're keen on feedback. You can respond here or use our 
form [2]. We do know that it doesn't handle PNG transparencies as well as it 
could (in IE), and it will disable some site's javascripts (but still seems 
to serve its purpose all the same). It works on sites using CSS (hex code 
colors, color names, or RGB) but won't work well on older sites using 
tags'n'tables. But then again the people who make sites like that probably 
wouldn't have much interest in this anyway.

The interface is new for me in a couple of ways. It's my first "fluid" site 
(I usually make fixed-width sites or jump right past fluid to elastic). It's 
also the first site I made to the XHTML 1.1 DTD. I'm sending it as 
application/xhtml+xml, but the browser is still processing the code as 
text/html (give me comments on this, please). It's also my first PHP-only 
site. I usually make PHP sites, but they have some PHP and some static 
mark-up. These pages are pure PHP, dynamic. First thing on the page is . Nary a break in between. You should find it very 
accessible and very usable. I took three days on this interface crossing my 
"t"s and dotting my "i"s.

It was a fun project.

Thanks in advance to all who have a look and comment one way or the other.

[1] http://graybit.com
[2] http://graybit.com/talk/


Sincerely,
Mike Cherim
http://green-beast.com/
http://accessites.org/






**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
**