W3C home > Mailing lists > Public > www-talk@w3.org > March to April 2001

W3C CUAP Recommendations: Mozilla Feedback

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 29 Mar 2001 14:58:09 -0800 (Pacific Standard Time)
To: <www-talk@w3.org>
cc: Karl Dubost <karl@w3.org>, Hugo Haas <hugo@w3.org>, Ian Jacobs <ij@w3.org>, <gerv@gerv.net>
Message-ID: <Pine.WNT.4.31.0103291437280.972-100000@HIXIE.netscape.com>

[The following text was written by Gerv, one of the Mozilla contributors.
I am forwarding this on Mozilla's behalf, as requested at the W3C XML
plenary in Boston. -- Ian]

Firstly, thank you very much for writing this. It has raised a number of
issues that were not on our radar at all and, although those are unlikely
to be addressed for Mozilla 1.0, they would never have been addressed had
you not pointed them out.

I found the document very useful, clear, easy to understand and easy to
file bugs about. I filed one bug for each recommendation in our bug system
to allow us to track implementation of these issues. The "simple
summaries" were extremely useful as titles for the bugs, and the
description of correct behaviour made a very good body for it.

Status as of 2001-03-28

The following is for your information. :-)

The following link will present a list of all the bugs in our bug system,
Bugzilla, which relate immediately to the W3C CUAP note. If a bug is
closed as a duplicate, you will need to look at the duplicate bug to
ascertain the status for that item.


Completely Implemented

1.3 Retrieve Web resources even if browser can't render
1.4 Allow choice of frames to print
1.13 Use the UI language as the default for language negotiation
2.2 Respect media descriptors when applying style sheets
2.3 If a style sheet is missing, ignore it and continue processing
3.2 Respect Content-Type HTTP header
3.3 Respect the character set of a resource when one is given
4.1 Handle the fragment identifier when request is redirected

Partly Implemented

1.9 allow the user to view all metadata

Many metadata attributes are already visible, and there's a patch pending
in the above bug which adds some more. The Page Info dialog also provides
several alternative views of the page, and exposes a great deal of

2.1 Implement user style sheets; allow disabling.

We already implement user style sheets, but there's no UI for them yet. We
currently don't do disabling.

1.5 Allow the user to add new URI schemes in a straightforward way.

This has been implemented as an addon, Protozilla
(http://protozilla.mozdev.org) and we are hoping to integrate it into the
main tree before 1.0.


1.11 Allow the user to bookmark negotiated resources

The current view is that this would be problematic (and probably confusing
to the user.) Please read the bug for more details, and argue your corner

1.12 Allow the user to choose among supported transfer encodings

There was some confusion as to exactly what was meant - please read the
bug for details. Improved support for transfer encodings has been mooted,
and may well happen. After that, this could be implemented.

3.6 List only supported media types in an HTTP Accept header.

This has caused great controversy :-) In March 2000 Mozilla silently began
sending */*, and a comment in the source indicated that "MIME based
content negotiation is dead." Many people don't agree, and are attempting
to get the situation improved. However, there is a wish to avoid sending
very long (>4k) Accept headers. A compromise will, hopefully, be reached,
but it's very unlikely that Mozilla will send its full Accept header.

Some input from the W3C on a suitable Accept: header would be welcome :-)


The rest :-)

Received on Thursday, 29 March 2001 17:55:56 UTC

This archive was generated by hypermail 2.4.0 : Monday, 20 January 2020 16:08:25 UTC