This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16418 - editorial - change "is to be" to "SHOULD be" in warning text
Summary: editorial - change "is to be" to "SHOULD be" in warning text
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL: http://dev.w3.org/2006/webapi/WebIDL/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-18 08:14 UTC by Glenn Adams
Modified: 2012-03-19 21:49 UTC (History)
3 users (show)

See Also:

Attachments

Description Glenn Adams 2012-03-18 08:14:15 UTC 
in Warning in 3.2, suggest changing "Instead, a callback is to be used." to read "Instead, a callback SHOULD be used."
Comment 1 Cameron McCormack 2012-03-19 08:36:57 UTC 
There was a reason in my mind why I used that wording when I wrote it, but I don't remember it now.  Anyway, fixed now.
Comment 2 Anne 2012-03-19 13:36:07 UTC 
Are warnings not supposed to be non-normative?
Comment 3 Cameron McCormack 2012-03-19 21:49:46 UTC 
Warnings are meant to be normative: http://dev.w3.org/2006/webapi/WebIDL/#conventions