Looking for input on my site (exciting stuff here)...
Posted: Sat May 12, 2007 12:28 am
I've been working on my site since 1998 and I've just completed the second preview of the 28th version of my site.
I'm looking for input about what people like, don't like, what people would like to see, and help me find anything that does not work clientside.
My preview is...
- XHTML 1.1 served as application/xhtml+xml except where not supported (in which case XHTML 1.0 Strict as text/html)
- Tableless layout, no console errors for XHTML, CSS, or JavaScript on any and all the Windows browsers I've tested.
- Passes any and all validators I've thrown at it including WAI AAA compliancy.
- Completely modularized JavaScript, allows me to add additional DHTML libraries in the future without any conflict or console errors.
- My site uses browser patching and so I've patched Opera 3+, IE 4+, Konqueror, and Gecko 1.7 and earlier.
- Site works good enough to navigate in Opera 4+, IE 5+, all Gecko, Konqueror.
- My site makes use of proprietary features and CSS3 where supported and served only to supporting browsers.
A couple interesting notes...
1.) My site compared between IE6 and Konqueror puts the KHTML rendering engine to shame as far as the browsers ability to support stuff (was not intended but interesting). Both require browser patching though when removed KHTML is superior as the page (while the text-size is bloated) layout remains mostly in tact.
2.) There are some interesting issues with very specific versions of Opera that I am aware of and actively pursuing (such as prompts (layers) not correctly opening in Opera 9.2 but working fine in 9.1.)
Things to keep in mind that you can do to manipulate the site and see what a difference some of the stuff does...
1.) In older browsers that do not support JavaScript, layers, etc you can manually enable and disable stuff by adding ?browserpatch=0 and you can enable browser patch again by adding ?browserpatch=1. Be sure you remove any ampersands from the end of the URL when doing so (since you may be doing this manually).
2.) Keep in mind my site is intended to be cutting edge so I'm not avoiding things that one might not do with a business site for example. In a way you can look at this like you look at Acid2 only this will eventually become my live site which is just over one year old by comparison.
3.) The site is not yet humanized...so to see some of the cool stuff you have to work with it manually. For example I have a URI catcher for errors, both invalid values for valid properties (index.php?audio=5) and invalid properties too (index.php?error).
The following link will automatically enable DHTML though it will hardly add more then a negligible wait to those on dialup at this point in time...
http://www.jabcreations.net/index.php?d ... ine=jquery
Remember so far compared to my main site (http://www.jabcreations.com/) I've been working on cross browser compatibility and additional functions. One thing on the personal toolbar (on the right sidebar) the themes menu, does technically work however where PHP would serve the other themes currently only serves classic (though all all other related functions still work correctly).
I'm interested in any criticisms people have but if you don't like something please reply with tact. Thanks!
I'm looking for input about what people like, don't like, what people would like to see, and help me find anything that does not work clientside.
My preview is...
- XHTML 1.1 served as application/xhtml+xml except where not supported (in which case XHTML 1.0 Strict as text/html)
- Tableless layout, no console errors for XHTML, CSS, or JavaScript on any and all the Windows browsers I've tested.
- Passes any and all validators I've thrown at it including WAI AAA compliancy.
- Completely modularized JavaScript, allows me to add additional DHTML libraries in the future without any conflict or console errors.
- My site uses browser patching and so I've patched Opera 3+, IE 4+, Konqueror, and Gecko 1.7 and earlier.
- Site works good enough to navigate in Opera 4+, IE 5+, all Gecko, Konqueror.
- My site makes use of proprietary features and CSS3 where supported and served only to supporting browsers.
A couple interesting notes...
1.) My site compared between IE6 and Konqueror puts the KHTML rendering engine to shame as far as the browsers ability to support stuff (was not intended but interesting). Both require browser patching though when removed KHTML is superior as the page (while the text-size is bloated) layout remains mostly in tact.
2.) There are some interesting issues with very specific versions of Opera that I am aware of and actively pursuing (such as prompts (layers) not correctly opening in Opera 9.2 but working fine in 9.1.)
Things to keep in mind that you can do to manipulate the site and see what a difference some of the stuff does...
1.) In older browsers that do not support JavaScript, layers, etc you can manually enable and disable stuff by adding ?browserpatch=0 and you can enable browser patch again by adding ?browserpatch=1. Be sure you remove any ampersands from the end of the URL when doing so (since you may be doing this manually).
2.) Keep in mind my site is intended to be cutting edge so I'm not avoiding things that one might not do with a business site for example. In a way you can look at this like you look at Acid2 only this will eventually become my live site which is just over one year old by comparison.
3.) The site is not yet humanized...so to see some of the cool stuff you have to work with it manually. For example I have a URI catcher for errors, both invalid values for valid properties (index.php?audio=5) and invalid properties too (index.php?error).
The following link will automatically enable DHTML though it will hardly add more then a negligible wait to those on dialup at this point in time...
http://www.jabcreations.net/index.php?d ... ine=jquery
Remember so far compared to my main site (http://www.jabcreations.com/) I've been working on cross browser compatibility and additional functions. One thing on the personal toolbar (on the right sidebar) the themes menu, does technically work however where PHP would serve the other themes currently only serves classic (though all all other related functions still work correctly).
I'm interested in any criticisms people have but if you don't like something please reply with tact. Thanks!