Comments (3)
I believe we should reuse the DOMException
types, if the API just needs a way to represents an error, with no additional data (such as in the MediaStreamError
's case, constraintName
) beyond the optional message
that can be used to convey user agent-defined human readable details of the error for debugging purposes.
For example, we could simply throw NotSupportedError
in both the cases.
I'll tag this for F2F discussion, since this should be a relatively quick one.
from presentation-api.
I would also be in favor of re-using DOMException
in the spec and using the human-readable message to provide the exact issue to the developer.
Unless there are arguments otherwise, we'll close this issue when the spec has been updated to throw DOMException
types for error cases.
from presentation-api.
@mfoltzgoogle Sounds good. I'd consider this a minor change that aligns the spec with the platform conventions.
Please feel free to submit a PR with "Fixes #78" in the commit message and merge it. That should automatically close the issue (thanks to https://help.github.com/articles/closing-issues-via-commit-messages/).
If any of the group participants have concerns with the change, we can always reopen the issue.
from presentation-api.
Related Issues (20)
- Uncaught ReferenceError: PresentationRequest is not defined HOT 5
- send request stuck on presentationRequest.getAvailability() Method HOT 1
- PresentationRequest is not defined? HOT 2
- Same-screen presentation HOT 9
- Requesting enhancements to the presentation API HOT 7
- HTTP header customization when fetching the presentation page
- reconnect after termination HOT 2
- Possibility for UA to close the connection when it is no longer operational HOT 3
- Publish a Candidate Recommendation Draft HOT 6
- Presentation-api cast file working good on Chrome version 87, but it is not work on Chrome version 88 HOT 13
- Presentation API cast app ID's broken on chromium 95 HOT 2
- update status for issue #347 (Local Presentation API to enable child-window presentation documents) HOT 1
- Presentation of objects prototyping HOT 2
- Update spec language around 1-UA mode to reflect Multi-Screen Window Placement HOT 1
- PresentationRequest.getAvailability() could always return a new Promise
- Update spec language to refer to child navigables instead of nested browing contexts?
- Cannot find name 'PresentationRequest' HOT 2
- "Deploy Pages" GitHub action is timing out HOT 2
- Cannot present on multiple devices from the same tab HOT 4
- Update the link to the HTTP spec HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from presentation-api.