W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2008

[Bug 5773] Authors need more control over handling of linked resources

From: <bugzilla@wiggum.w3.org>
Date: Fri, 20 Jun 2008 08:33:44 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1K9c40-0005Fi-LJ@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5773





--- Comment #11 from Julian Reschke <julian.reschke@gmx.de>  2008-06-20 08:33:44 ---
(In reply to comment #10)
> The HTTPWG's, I guess. Who works on the relevant RFC?

Well, the RFCs already specify the solution. HTTPbis can potentially *clarify*
it, but that's it.

The problem is that some browser vendors aren't listening.

> Interoperability should be the (only) concern of every working group. But only
> within the scope of the work of that working group. It shouldn't be the HTTP
> WG's job to make UAs interoperable for CSS and ODF, for example. Or the HTML
> WG's job to make UAs interoperable over HTTP. (HTML5 oversteps its bounds in an
> attempt to prevent cracks appearing between the specs, or to cover things that
> other working groups want to ignore, like content-sniffing, but ideally the
> specs would all be comprehensive and "flush", to extend the metaphor.)

Yes, in theory everything should be orthogonal, but in practice it isn't.

The really simple question is: what is needed to make Apple and Microsoft
implement what's already specified? If the HTML WG (or the W3C in general)
could help, that would be great.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 20 June 2008 08:34:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 20 June 2008 08:34:19 GMT