From 53bf7674819dd345b098e407ce62fba174cae3ca Mon Sep 17 00:00:00 2001
From: Kai Ninomiya <kainino@chromium.org>
Date: Mon, 11 Nov 2019 20:58:47 +0000
Subject: [PATCH] Expose limits on the adapter (#489)

There's no reason to leave this out anymore.
Implementations can implement it whenever they want.
---
 spec/index.bs | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/spec/index.bs b/spec/index.bs
index f9089b901a..91c0d786c3 100644
--- a/spec/index.bs
+++ b/spec/index.bs
@@ -328,7 +328,7 @@ and exposes its capabilities (extensions and limits).
 interface GPUAdapter {
     readonly attribute DOMString name;
     readonly attribute object extensions;
-    //readonly attribute GPULimits limits; Don't expose higher limits for now.
+    readonly attribute object limits;
 
     // May reject with DOMException  // TODO: DOMException("OperationError")?
     Promise<GPUDevice> requestDevice(optional GPUDeviceDescriptor descriptor = {});
@@ -354,6 +354,11 @@ interface GPUAdapter {
             not by the [=adapter=], it will be `false`.
           - If an extension is supported by the user agent and
             by the [=adapter=], it will be `true`.
+
+    : <dfn>limits</dfn>
+    ::
+        A {{GPULimits}} object which exposes the maximum limits supported
+        by the adapter.
 </dl>
 
 {{GPUAdapter}} also has the following internal slots: