Skip to content
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

Editorial: Include "legacy" in the name of entry and incumbent #4229

Closed
wants to merge 1 commit into from

Conversation

littledan
Copy link
Contributor

@littledan littledan commented Dec 10, 2018

Hopefully this will help discourage people from using them.

Also remove "entry global object" as it seemed to be unused.

See #1430/#1431


💥 Error: Wattsi server error 💥

PR Preview failed to build. (Last tried on Jan 15, 2021, 7:59 AM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.

🔗 Related URL

<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.10.3</center>
</body>
</html>

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

Hopefully this will help discourage people from using them.

Also remove "entry global object" as it seemed to be unused.

See whatwg#1430/whatwg#1431
@littledan
Copy link
Contributor Author

cc @domenic

@annevk
Copy link
Member

annevk commented Feb 22, 2019

I skimmed through this patch (apologies for the delay), main problems I see:

  • Exceeding the 100column limit due to search & replace
  • Breaking external callers

I don't think the latter is super problematic, but perhaps we should file downstream issues.

Base automatically changed from master to main January 15, 2021 07:57
@annevk
Copy link
Member

annevk commented Apr 28, 2021

This still seems worthwhile, but I guess it got lost somehow. 😟 I suspect rebasing this is probably more trouble than it's worth though.

@domenic thoughts on what to do here?

@domenic
Copy link
Member

domenic commented Apr 28, 2021

Yeah, I can try to recreate this.

domenic added a commit that referenced this pull request May 20, 2021
This will discourage people from using it, helping with #1430. Closes #4229 by superseding it. Note that entry is already non-exported.
@annevk annevk closed this in #6702 May 21, 2021
annevk pushed a commit that referenced this pull request May 21, 2021
This will discourage people from using it, helping with #1430. Closes #4229 by superseding it. Note that entry is already non-exported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants