I think I like #3 as well. You could probably get the CMS to insert the
title of the post with a string: $title and it wouldn't require content
creators to do any extra work - it'd just insert whatever they used for
the title of the post.
What about for another common link which is 'Comments'?
On 23/09/2004, at 2:28 PM, Lea de Groot wrote:
On Thu, 23 Sep 2004 14:10:24 +1000, Justin French wrote:
3 read morespan on 'title of my post'/span then hide the span
with display:none; from modern browsers, while still having entirely
accessible source
No, wait - surely the image replacement
Okay, see 4 different techniques here:
http://design.quagma.net/test1.html
1. just the title attribute
2. display none
3. visibility hidden
4. left -5000px
I like #4
cameron.
Jake Badger wrote:
You could use the one of the techniques that current image replacement tricks
use: either set the width
Hello, everybody. I've been reading the list for a day or two, and I'm
very excited to be part of the growing number of designers/developers
who are taking a stand for standards.
A little bit about me: I am originally from Seattle, Washington, USA,
but moved to Portugal in April, 2003, in order
James wrote:
I found the Flash satay markup worked fine on every browser I tested on
with every Flash player version I could find.
Unfortunately that's not my experience. :-(
All the best,
--
Ian
**
The discussion list for
I wrote:
Unfortunately it seems the best solution is to use JavaScript to detect
the existence (and correct version) of flash and then use document.write
to deliver the appropriate object or embed. Only safari seems to have a
problem.
Actually it looks like I got that wrong. Safari is
Mark wrote:
Unless there is a major reason to be XHTML then I normally use HTML
4.01 - even if only on the pages with flash included.
That's what I'm going to do now :-(
Thanks for the help everyone!
All the best,
--
Ian
**
The discussion
Just checked it in:
PC: Opera v7, Firefox v1, IE v6.
Mac: Safari v1, firefox v1, Netscape v7, IE v5.2
All displayed just fine.
I'd remind you to replace some of the alt tags though (intro1.jpg etc).
And perhaps consider adding house doctor to the initial h1.
mike 2k:)2
marqueeblink
e-mail:
Hi Mike,
Just checked it in:
PC: Opera v7, Firefox v1, IE v6.
Mac: Safari v1, firefox v1, Netscape v7, IE v5.2
All displayed just fine.
Great - many thanks!
I'd remind you to replace some of the alt tags though (intro1.jpg etc).
The client controls those. I'll remind them to make their
I'd remind you to replace some of the alt tags though
(intro1.jpg etc).
The client controls those. I'll remind them to make their alt tags
accessible.
They're attributes...ATTRIBUTES...not tags!
Sorry, bit of a rant. Feel better now ;)
Patrick
This is a bit off topic (sorry) but we need your support once again to make XStandard
for Mozilla/Firefox even better.
The guys at Mozilla Foundation have been real helpful, but Firefox still has a bug
that makes integrating plug-ins like XStandard a bit of a kluge (compared to IE). So
we
Patrick wrote:
The client controls those. I'll remind them to make their alt tags
accessible.
They're attributes...ATTRIBUTES...not tags!
I know that... You know that... but to a client, they're alt tags :-)
All the best,
--
Ian
**
Hi Everyone
Opera is definately not in my scope of expertise. I've fixed the vast majority of my
css bugs and now I need to fix a couple Opera problems.
Here are some screen shots from browsercam. I hope you can view them.
http://www.browsercam.com/projects/99910/1643010.jpg
hey, welcome to the club!happy transition to css2.
- Original Message -
From: john [EMAIL PROTECTED]
Date: Thu, 23 Sep 2004 11:27:46 +0100
To: [EMAIL PROTECTED]
Subject: [WSG] introduction
Hello, everybody. I've been reading the list for a day or two, and I'm
very excited to be part of
Reiterating Ben's comments and Zeldman's summary of the problems with the
Satay method in Designing With Web Standards, that's exactly the problem
with the Satay--sometimes it works and sometimes it doesn't. On some
browsers, on some machines, sometimes. I think Zeldman's comment is how many
The CSS-discuss Wiki is a very good wealth of CSS information that is
always being updated:
http://css-discuss.incutio.com/?page=FrontPage
Original Message
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: [WSG] CSS rules quirks database
Date: Thu, 23 Sep 2004 16:07:29 -0700
I thoroughly agree with David here. Web standards are a means to an end and
not an end in themselves. The way I see it, the point of web standards is to
a) separate form from content and both from behaviour; b) make all content
equally accessible to the widest possible audience; c) provide a
Hi Paul,
I created a list of CSS properties and browsers that support them
http://www.csscreator.com/attributes/
It still needs a little work refining and adding content.
The idea was to get the community (members of the CSS Forum) behind it
and have them add to the content.
Once logged in you
On Fri, 24 Sep 2004 09:43:31 +1000, Kevin Futter
[EMAIL PROTECTED] wrote:
I thoroughly agree with David here. Web standards are a means to an end and
not an end in themselves. The way I see it, the point of web standards is to
a) separate form from content and both from behaviour; b) make all
At 05:00 PM 9/23/2004, Tony Aslett wrote:
I created a list of CSS properties and browsers that support them
http://www.csscreator.com/attributes/
Excellent work, Tony. Are you storing this in an SQL database?
I'd like to see some other layers of information added to a database such
as yours.
Hello Rimantas,
Well said and, IMHO, absolutely correct.
--
Best regards,
Ric
Water Stone
mailto:[EMAIL PROTECTED]
visit our sites: www.waterandstone.com
www.researchlaunchpad.com
www.balitravelportal.com
Friday, September 24, 2004, 8:26:21 AM, you
Paul Novitski wrote:
At 05:00 PM 9/23/2004, Tony Aslett wrote:
I created a list of CSS properties and browsers that support them
http://www.csscreator.com/attributes/
Excellent work, Tony. Are you storing this in an SQL database?
Thanks Paul,
Yes it's stored in a MySQL database.
I'd like to see
At 10:40 AM +1000 24/9/04, Daniela Meleo wrote:
He wants me to change the site so that it uses frames. The local nav would
be in the left frame the global nav content divs in the right.
At this point I want to stop you and say surely you must be able to
avoid having frames and use some kind of
Ric wrote:
Hello Rimantas,
Well said and, IMHO, absolutely correct.
Anyone notice Zeldman's recently announcement of happycog's redesign of the
KC Chiefs site? He wrote that the website is standards-compliant but added a
disclaimer that read:
Attention XHTML nit-pickers: We are still in the
John Horner said:
That's not the case, luckily. Can you say how you came to that
understanding?
John , that's a relief. I (in a slight panic) found this article
http://www.sitepoint.com/article/frames-frame-usage-explained/3
around the sixth paragraph, it notes that head info shouldn't be
Ian Fenn wrote:
I wrote:
Anyone notice Zeldman's recently announcement
Sorry for the typo. It's 2.40am here in the UK. Time to get some shut-eye.
Kids nowadays...no staying power. ;)
Patrick
_
re·dux (adj.): brought back; returned. used
I raised SSIs, which are beyond my skill to develop
I can absolutely assure you that they aren't, really!
but for various reasons that won't be an option.
Just in case that's another misconception, would you like to say what
the reasons are?
Daniela Meleo wrote:
I raised SSIs, which are beyond my skill to develop, but for various
reasons that won't be an option.
? include(whatever.html); ?
That's all you have to do, (and change the extension from .html to
.php). You'll need a web server with php enabled, I don't see why that
would
Patrick wrote:
Kids nowadays...no staying power. ;)
Don't be so sure ;-)
--
Ian
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration,
On Friday, Sep 24, 2004, at 10:40 Australia/Sydney, Daniela Meleo wrote:
NOW, the client has decided that after handover he will need the
ability to
easily add new pages whenever he needs to (as additional topics not yet
know become required.) He's an open source techie type and will hand
code
This thread has been a bit of deja vu for me. I have been discussing
this problem with an external developer who uses Satay, who doesn't seem
to believe that it is flaky. He has tested it across many browsers/OS's
and hasn't seen the problem, and therefore had difficulty believing
there is a prob.
At the risk of over Zeldmanning the discussion...
My previous comment was probably (ok definitely) influenced by Zeldman's
August 12 posting Silence and Noise
http://www.zeldman.com/daily/0804b.shtml
The original idea behind the Web Standards Project which really kicked off
the whole web standards
David McKinnon wrote:
I've used Ian Hixie's method, because it seems to be the least problematic.
David
One of the central tenets of good coding is that comments are for
comments, code is for code. It's bad practice to put code into comments.
Comments should not be interpreted by any software,
33 matches
Mail list logo
