W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2000

Re: CSS and implementation

From: Charles McCathieNevile <charles@w3.org>
Date: Tue, 1 Feb 2000 03:12:29 -0500 (EST)
To: Robert Neff <robneff@home.com>
cc: w3c-wai-gl@w3.org, Wendy A Chisholm <wendy@w3.org>
Message-ID: <Pine.LNX.4.20.0002010310240.11747-100000@tux.w3.org>
I don't think so. We state already that it is a good idea to use valid
markup, and meta http-equiv="refresh" is not valid since it does not conform
to the http spec that it relies on, as I understand it.

It might be worth putting into the techniques document though, as an example
of problems that can be caused when moving away from validity. (other
problems occur when people use a validating browser, such as a real XML
parser which can interpret XHTML 1.0 - currently the W3C's recommendation for
how to do HTML.

Charles McCN

On Mon, 31 Jan 2000, Robert Neff wrote:

  should we put this in the errata...beware of meta refresh when using CSS?
  
  ----- Original Message -----
  From: Charles McCathieNevile <charles@w3.org>
  To: Robert Neff <robneff@home.com>
  Cc: <w3c-wai-gl@w3.org>; Wendy A Chisholm <wendy@w3.org>
  Sent: Monday, January 31, 2000 5:21 PM
  Subject: Re: CSS and implementation
  
  
  > Meta refresh relies on a browser interpreting a command that is
  masquerading
  > as an http header, although ther is in fact no such header. SO it isn't
  that
  > surprising that it causes problems.
  >
  > Charles McCN
  >
  > On Sat, 29 Jan 2000, Robert Neff wrote:
  >
  >   ON the two items i wrote previously.
  >
  >   1.  We may have resolved the problem with documentum.  Not 100% yet.
  >   2.  The CSS was blowing up on many PCs using various browsers - yet you
  >   could surf anywhere on the internet and be fine.  The cause was meta
  >   refresh.  Removed it and everyone had access.
  >
  >   go figure?
  >
  >   > At 09:01 AM 1/23/00 , Robert Neff wrote:
  >   > >We are implementing CSS on the intranet and have seen two snafus that
  we
  >   are
  >   > >looking at now.
  >   > >
  >   > >1.  We use Documentum, a electroninc document management system, as
  our
  >   > >document delivery system.  It has a server piece that sits on the web
  >   server
  >   > >and queries the document database for documents.  On the CSS page is
  an
  >   > >embedded query that starts the Documentum server piece and returns
  the
  >   > >documents.  This is not working well with CSS.  It is blowing up on
  IE 5
  >   and
  >   > >locking upnon IE 4.
  >   > >
  >   > >2.  We have a simple intranet with headers and footers and inlcudes
  for
  >   each
  >   > >and we have applicaitons.  We also are having serious problems
  >   implementing
  >   > >the CSS as is does not work well or not at all on all builds of
  Micorsoft
  >   > >Internet Explorer.  This is causing us to reinstall Micorsoft
  Internet
  >   > >Explorer.
  >   > >
  >   > >CSS is not integrating well and we are troubledhooting to see what
  the
  >   > >problem is.  For exmaple we are building a simple HTML page to test
  >   > >fucntionality with th browsers.
  >   > >
  >   > >Anyone else having problems like this?
  >   > >
  >   > >rob
  >   >
  >   > --
  >   > wendy a chisholm
  >   > world wide web consortium
  >   > web accessibility initiative
  >   > madison, wi usa
  >   > tel: +1 608 663 6346
  >   > /--
  >   >
  >
  >
  > --
  > Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134
  136
  > W3C Web Accessibility Initiative
  http://www.w3.org/WAI
  > 21 Mitchell Street, Footscray, VIC 3011,  Australia
  >
  

--
Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
21 Mitchell Street, Footscray, VIC 3011,  Australia 
Received on Tuesday, 1 February 2000 03:12:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:01 GMT