W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 16544] Clarify frame handling for frame based encryption

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Oct 2012 22:21:01 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-16544-2486-2Ea3Ycf9oO@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16544

--- Comment #4 from sz.bugzilla@gmail.com ---
Another recommendation for this bug is clarifying the purpose of API in the
diagram.  Currently the diagram is not explicitly mentioning which API is in
the scope of the proposal and which one is not.  The decrypted frame API is a
great example.  The API is not the scope of the proposal but it is one of use
cases on how the decrypted frame can be handled.  I strongly recommend to add
another indicator on the diagram which tells if the API is proposed API from
the proposal or not.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 22 October 2012 22:21:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 October 2012 22:21:03 GMT