[css-font-loading] Add an issue about the internal ES objects and their pristine-ness.

Author: tabatkins

css-font-loading/Overview.bs

@@ -33,6 +33,15 @@ Introduction</h2>
 	It also provides methods to track the loading status of an individual font,
 	or of all the fonts on an entire page.
 
+	Issue: Several things in this spec use normal ES objects to define behavior,
+	such as various things using Promises internally,
+	and FontFaceSet using a Set internally.
+	I believe the intention here is that these objects
+	(and their prototype chains) are pristine,
+	unaffected by anything the author has done.
+	Is this a good intention?
+	If so, how should I indicate this in the spec?
+
 <h3 id="values">
 Values</h3>
 

css-font-loading/Overview.html

@@ -54,7 +54,7 @@
 </p>
   <h1 class="p-name no-ref" id=title>CSS Font Loading Module Level 3</h1>
   <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
-    <span class=dt-updated><span class=value-title title=20140627>27 June 2014</span></span></span></h2>
+    <span class=dt-updated><span class=value-title title=20140630>30 June 2014</span></span></span></h2>
   <div data-fill-with=spec-metadata><dl>
 	<dt>This version:
 	<dd><a class=u-url href=http://dev.w3.org/csswg/css-font-loading/>http://dev.w3.org/csswg/css-font-loading/</a>
@@ -178,6 +178,15 @@ <h2 class="heading settled heading" data-level=1 id=introduction><span class=sec
 	It also provides methods to track the loading status of an individual font,
 	or of all the fonts on an entire page.</p>
 
+<p class=issue id=issue-531209c4><a class=self-link href=#issue-531209c4></a>Several things in this spec use normal ES objects to define behavior,
+	such as various things using Promises internally,
+	and FontFaceSet using a Set internally.
+	I believe the intention here is that these objects
+	(and their prototype chains) are pristine,
+	unaffected by anything the author has done.
+	Is this a good intention?
+	If so, how should I indicate this in the spec?</p>
+
 <h3 class="heading settled heading" data-level=1.1 id=values><span class=secno>1.1 </span><span class=content>
 Values</span><a class=self-link href=#values></a></h3>
 
@@ -1338,7 +1347,16 @@ <h2 class="no-num no-ref heading settled heading" id=property-index><span class=
 <div data-fill-with=property-index><p>No properties defined.</div>
 
 
-<h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><div class=issue>Need to define the base url,
+<h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><div class=issue>Several things in this spec use normal ES objects to define behavior,
+	such as various things using Promises internally,
+	and FontFaceSet using a Set internally.
+	I believe the intention here is that these objects
+	(and their prototype chains) are pristine,
+	unaffected by anything the author has done.
+	Is this a good intention?
+	If so, how should I indicate this in the spec?<a href=#issue-531209c4> ↵ </a></div>
+
+<div class=issue>Need to define the base url,
 			so relative urls can resolve.
 			Should it be the url of the document?
 			Is that correct for workers too,