This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Consider including issue markers in drafts for issues that have been closed without prejudice. Based on a suggestion from Larry Masinter in bug 9187.
(In reply to comment #0) > Consider including issue markers in drafts for issues that have been closed > without prejudice. I see no purpose to doing so. I'd like issue markers to indicate things where people have actual proposals or are actively working to produce one. I see no need to indicate inline places where there might (or might not) be future work in subsequent releases of HTML.
(In reply to comment #1) > (In reply to comment #0) > > Consider including issue markers in drafts for issues that have been closed > > without prejudice. > > I see no purpose to doing so. > > I'd like issue markers to indicate things where people have actual proposals or > are actively working to produce one. I see no need to indicate inline places > where there might (or might not) be future work in subsequent releases of HTML. > I agree. While there may be value to exposing a list of ideas for the future, inline markers in the draft do not seem like the most effective or useful way to do that.
Rejected per agreement of the Chairs.