[Bug 16442] Extreme length of single page spec causes long load time/unresponsive browser, decreases effectiveness of spec.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16442

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |travil@microsoft.com
         Resolution|---                         |WONTFIX

--- Comment #7 from Travis Leithead [MSFT] <travil@microsoft.com> ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:


   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: Spec can still be quite long
Rationale: 

In quick searches, the multi-page spec does come up frequently as the first
search result. In any case, the multi-page/single page selection option is
nearly the first thing in the opening boilerplate, so it should be easy to
quickly get to the fast-loading split-up spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 21 March 2013 23:44:50 UTC