W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 6610] add a preventable forced-fragment method

From: <bugzilla@wiggum.w3.org>
Date: Sun, 28 Mar 2010 19:48:47 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NvyTX-00071E-1x@wiggum.w3.org>

Maciej Stachowiak <mjs@apple.com> changed:

           What    |Removed                     |Added
                 CC|                            |mjs@apple.com

--- Comment #7 from Maciej Stachowiak <mjs@apple.com>  2010-03-28 19:48:46 ---
(In reply to comment #6)
> This would help users find more content and find it faster, even when a page
> author has not created a fragment. I'm requesting escalation.

It's incorrect process to both reopen the bug *and* request escalation. Please
pick one of the following:

1) Reopen bug for fresh consideration by the editor - you will get a full
Editor's Response with rationale and a spec diff link if any spec changes are

2) Escalate to tracker for consideration by the full Working Group - a Change
Proposal will be required.

In case of (1), the TrackerRequest keyword should be removed for now (you will
still be entitled to request escalation once the editor replies again).

In case of (2), the bug should be moved back to VERIFIED - it will remain there
and will not be closed pending a Working Group Decision.

If you do not pick one of these in a couple of days, I will assume option 2.

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, 28 March 2010 19:48:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:48 UTC