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

Missing String Row in ToObject Conversions Table on ECMAScript Specification 2023 PDF #3267

Open
aszx87410 opened this issue Jan 24, 2024 · 4 comments

Comments

@aszx87410
Copy link

aszx87410 commented Jan 24, 2024

Description

I have observed an issue in the ECMAScript 2023 PDF version regarding the ToObject Conversions table. It appears that there is a missing row in the PDF version compared to the HTML version.

This issue impacts clarity and completeness when referring to the ECMAScript 2023 specification in PDF format. I suspect it might be a bug in converting HTML to PDF, and it could potentially affect other parts/versions as well. I'm not sure if reporting it here is correct; if it's not, please let me know where I should report it. Thanks!

Steps to Reproduce

  1. Open the ECMAScript 2023 specification in PDF format: https://ecma-international.org/wp-content/uploads/ECMA-262_14th_edition_june_2023.pdf
  2. Navigate to the ToObject Conversions table section.(p.74)
  3. Compare the table in the PDF with the one in the HTML version.

Expected Behavior

The ToObject Conversions table in the PDF version should have the same data as the HTML version.

Actual Behavior

There is a missing row in the ToObject table of the ECMAScript 2023 PDF specification, which is present in the HTML version.

HTML:
截圖 2024-01-24 下午9 23 28

PDF(Argument Type String is missing):
截圖 2024-01-24 下午9 22 54

@jmdyck jmdyck changed the title Missing String Column in ToObject Conversions Table on ECMAScript Specification 2023 PDF Missing String Row in ToObject Conversions Table on ECMAScript Specification 2023 PDF Jan 24, 2024
@jmdyck
Copy link
Collaborator

jmdyck commented Jan 24, 2024

"Row" rather than "Column", but yes, well spotted.

@aszx87410
Copy link
Author

@jmdyck thanks 🙏, updated.

@ljharb
Copy link
Member

ljharb commented Jan 24, 2024

cc @allenwb

@ecmageneva
Copy link

Thanks. I have already informed this afternoon Allen and Patrick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants