chore(docs): migrate & document all Page events (#6154)

* chore(docs): migrate & document all Page events

Rather than a generic `Events.ts` file we can instead document events as
an enum within each individual class. It's easier to document and work
with, and it's clearer where events originate from.
This commit is contained in:
Jack Franklin
2020-07-06 11:34:55 +01:00
committed by GitHub
parent e67a860eb0
commit ba7624a6df
5 changed files with 168 additions and 28 deletions

View File

@@ -4,7 +4,7 @@
## Page class
Page provides methods to interact with a single tab or \[extension background page\](https://developer.chrome.com/extensions/background\_pages) in Chromium. One \[Browser\] instance might have multiple \[Page\] instances.
Page provides methods to interact with a single tab or [extension background page](https://developer.chrome.com/extensions/background_pages) in Chromium.
<b>Signature:</b>
@@ -15,6 +15,8 @@ export declare class Page extends EventEmitter
## Remarks
One Browser instance might have multiple Page instances.
The constructor for this class is marked as internal. Third-party code should not call the constructor directly or create subclasses that extend the `Page` class.
## Example 1