- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 22 Jun 2008 08:43:58 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5773
Rob Burns <rob@robburns.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NEEDSINFO |
--- Comment #25 from Rob Burns <rob@robburns.com> 2008-06-22 08:43:58 ---
(In reply to comment #24)
> Ok.
> I'm marking this NEEDSINFO as we need the following information:
> - whether this is something that authors really want
> - why what they have now doesn't work and how they are working around those
> problems
These points were included in the linked URL:
http://esw.w3.org/topic/HTML/LinkAndEmbeddingAttributes
In short, authors right now provide detailed platform specific instructions
(wrong for anyone using a different platform) on how to click on the link to
download the resource. Obviously using @target or anything like that need
author discretion and authors should notify users of the non-standard handling
of the link. But that shouldn't stop us from providing the functionality for
users and authors
> - which implementations have committed to implementing the feature
> experimentally
Again, this is the same canned response you use to dismiss proposals when you
can't think of anything else. Please stop using this tired old remark. It leads
us to reverse the priority of constituencies, especially on a feature like
this that is fairly rudimentary to implement.
If it helps, I'll personally do what I have in my power to see that two
implementations implement support for this markup.
Info needed, info provided!
--
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 Sunday, 22 June 2008 08:44:32 UTC