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

Fix ES5 errors (IE11) #82145

Merged
merged 1 commit into from
Feb 16, 2021
Merged

Fix ES5 errors (IE11) #82145

merged 1 commit into from
Feb 16, 2021

Conversation

GuillaumeGomez
Copy link
Member

rustdoc is supposed to run on IE11 but someone reported me that it wasn't. I just confirmed it by using es-check with the es5 option like this:

$ es-check es5 src/librustdoc/html/static/*.js

The PR fixes those issues and add CI checks to prevent regressions.

@Mark-Simulacrum: I added checks in the CI, but not sure if it's the correct way to do it. Any help on that side would be very appreciated!

r? @Nemo157

@GuillaumeGomez GuillaumeGomez added the T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. label Feb 15, 2021
@rust-highfive
Copy link
Collaborator

Some changes occurred in HTML/CSS/JS.

cc @GuillaumeGomez

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 15, 2021
@GuillaumeGomez GuillaumeGomez changed the title Es5 checks ES5 checks Feb 15, 2021
@Nemo157
Copy link
Member

Nemo157 commented Feb 15, 2021

rustdoc is supposed to run on IE11

My reading of the browser minimums RFC was that it wasn't, Edge is the minimum supported Windows-builtin browser.

@GuillaumeGomez
Copy link
Member Author

It always has been (well, until recent changes). The whole code has been made like this in order to support it after all.

@rust-log-analyzer

This comment has been minimized.

@GuillaumeGomez GuillaumeGomez force-pushed the es5-checks branch 3 times, most recently from f1c1124 to 30f0c91 Compare February 15, 2021 10:04
@rust-lang rust-lang deleted a comment from rust-log-analyzer Feb 15, 2021
@GuillaumeGomez GuillaumeGomez force-pushed the es5-checks branch 2 times, most recently from 68dd4e5 to 6a8809d Compare February 15, 2021 10:34
@rust-lang rust-lang deleted a comment from rust-log-analyzer Feb 15, 2021
Copy link
Contributor

@pickfire pickfire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

By the way, happy chinese new year!

@GuillaumeGomez
Copy link
Member Author

Fixed the nits. Seems like it's ready @Mark-Simulacrum

@GuillaumeGomez
Copy link
Member Author

I removed the second commit and will open another PR so this fix can be merged quickly.

@bors: r=Nemo157 rollup

@bors
Copy link
Contributor

bors commented Feb 16, 2021

📌 Commit 719c8d4 has been approved by Nemo157

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 16, 2021
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Feb 16, 2021
ES5 checks

rustdoc is supposed to run on IE11 but someone reported me that it wasn't. I just confirmed it by using `es-check` with the `es5` option like this:

```
$ es-check es5 src/librustdoc/html/static/*.js
```

The PR fixes those issues and add CI checks to prevent regressions.

`@Mark-Simulacrum:` I added checks in the CI, but not sure if it's the correct way to do it. Any help on that side would be very appreciated!

r? `@Nemo157`
Dylan-DPC-zz pushed a commit to Dylan-DPC-zz/rust that referenced this pull request Feb 16, 2021
ES5 checks

rustdoc is supposed to run on IE11 but someone reported me that it wasn't. I just confirmed it by using `es-check` with the `es5` option like this:

```
$ es-check es5 src/librustdoc/html/static/*.js
```

The PR fixes those issues and add CI checks to prevent regressions.

``@Mark-Simulacrum:`` I added checks in the CI, but not sure if it's the correct way to do it. Any help on that side would be very appreciated!

r? ``@Nemo157``
@GuillaumeGomez GuillaumeGomez changed the title ES5 checks Fix ES5 errors (IE11) Feb 16, 2021
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 16, 2021
…laumeGomez

Rollup of 6 pull requests

Successful merges:

 - rust-lang#82145 (Fix ES5 errors (IE11))
 - rust-lang#82160 (Fix typo in rustc_infer::infer::UndoLog)
 - rust-lang#82161 (Add long explanation for E0545)
 - rust-lang#82163 (avoid full-slicing slices)
 - rust-lang#82175 (validation: fix invalid-fn-ptr error message)
 - rust-lang#82184 ([Minor] Update discriminant_value docs)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 4df0401 into rust-lang:master Feb 16, 2021
@rustbot rustbot added this to the 1.52.0 milestone Feb 16, 2021
@GuillaumeGomez GuillaumeGomez deleted the es5-checks branch February 17, 2021 08:53
JohnTitor added a commit to JohnTitor/rust that referenced this pull request Feb 21, 2021
…k-Simulacrum

Add check for ES5 in CI

Follow-up of rust-lang#82145.

r? `@Mark-Simulacrum`
JohnTitor added a commit to JohnTitor/rust that referenced this pull request Feb 21, 2021
…k-Simulacrum

Add check for ES5 in CI

Follow-up of rust-lang#82145.

r? ``@Mark-Simulacrum``
JohnTitor added a commit to JohnTitor/rust that referenced this pull request Feb 21, 2021
…k-Simulacrum

Add check for ES5 in CI

Follow-up of rust-lang#82145.

r? ```@Mark-Simulacrum```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants