New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Budget API #73

Closed
Jxck opened this Issue Mar 15, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@Jxck
Copy link

Jxck commented Mar 15, 2018

Request for Mozilla Position on an Emerging Web Specification

Other information

@martinthomson

This comment has been minimized.

Copy link
Member

martinthomson commented Mar 16, 2018

Having spoken to @beverloo about this, it seems like this is something that Google plan to decommission. As I noted in my feedback, there are simpler approaches to this, and Google are interested in exploring those further.

I don't think that this is harmful in the sense that this would damage the web ecosystem - at least any more than any other useless addition to the platform would be detrimental - so I think that "non-harmful" is what we should signal.

martinthomson added a commit to martinthomson/standards-positions that referenced this issue Mar 16, 2018

@dbaron

This comment has been minimized.

Copy link
Member

dbaron commented Mar 22, 2018

Sorry for missing the pull request here for a bit.

I guess I'm fine with the non-harmful label, although:

  • it seems like the use cases address real needs, but
  • on the flip side, I'd be a little worried that the API might overly constrain implementations simply because they'd be forced by uses of the API to adopt the same policies as the implementation that the developers were targeting. (This might be avoidable by carefully specifying what the budget numbers mean in a way that's more likely to lead to interoperability across different policies, but I don't think the current draft specifies it very carefully.)

@dbaron dbaron closed this in #75 Mar 22, 2018

dbaron added a commit that referenced this issue Mar 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment