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 15764 - Review notes for normative statements
Summary: Review notes for normative statements
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-28 17:59 UTC by Ms2ger
Modified: 2012-01-29 23:26 UTC (History)
2 users (show)

See Also:


Attachments

Description Ms2ger 2012-01-28 17:59:42 UTC
For example, there's a note that says

> Specification authors should avoid using callback interfaces that have
> only a single operation, unless required to describe the requirements
> of existing APIs. Instead, a callback should be used. 

It's not clear to me if this is normative, and if this recommendation is on the same level as the pink warnings, which seem to be similar in subject (legacycaller, integer constants...)
Comment 1 Cameron McCormack 2012-01-29 23:26:37 UTC
I upgraded that and another Note to a Warning, so that they are normative.