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

update definition of fontBoundingBoxAscent/Descent and emHeightAscent… #5429

Merged
merged 19 commits into from
Jun 29, 2020
Merged

update definition of fontBoundingBoxAscent/Descent and emHeightAscent… #5429

merged 19 commits into from
Jun 29, 2020

Conversation

yiyix
Copy link
Contributor

@yiyix yiyix commented Apr 2, 2020

Following in the conclusion in #4073, I have updated the spec for fontBoundingBoxAscent/Descent and emHeightAscent/Descent.


/acknowledgements.html ( diff )
/canvas.html ( diff )
/infrastructure.html ( diff )
/references.html ( diff )

source Outdated Show resolved Hide resolved
@annevk
Copy link
Member

annevk commented Apr 6, 2020

Could you clarify why this is only changing two instances of "line box"? Are the others still correct? If so, I think we should have a note explaining the situation as the resulting section ends up being a bit confusing.

@yiyix
Copy link
Contributor Author

yiyix commented Apr 17, 2020

You are right, I have updated all line box to inline box in TextMetrics. Thank you.

source Outdated Show resolved Hide resolved
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

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

So after this there are two remaining instances of line box in a different section. Are those still correct? Do they need a follow-up issue?

source Outdated Show resolved Hide resolved
source Outdated Show resolved Hide resolved
@yiyix
Copy link
Contributor Author

yiyix commented Jun 19, 2020

I have created a new issue to CSS for following up this conversation: #5656

Updated the note as requested.

@annevk
Copy link
Member

annevk commented Jun 25, 2020

@yiyix I would expect the issue to be against https://github.com/w3c/csswg-drafts.

Also, since it appears you work for Google you cannot sign the Participant Agreement as an individual.

source Outdated Show resolved Hide resolved
source Show resolved Hide resolved
@annevk
Copy link
Member

annevk commented Jun 26, 2020

@yiyix you need to make your (assumed) membership of https://github.com/googlers public in order for the Participation check to be able to pass.

source Outdated Show resolved Hide resolved
source Outdated Show resolved Hide resolved
source Outdated Show resolved Hide resolved
@annevk
Copy link
Member

annevk commented Jun 26, 2020

@jfkthame and I discussed this and found there are concepts defined in CSS Fonts already, which we're now using. I filed w3c/csswg-drafts#5266 to ensure those concepts stick around.

At this point this could use a final round of review from @yiyix / @fserb (given the many changes) and @domenic.

@annevk annevk requested review from fserb and domenic June 26, 2020 15:12
@annevk annevk added clarification Standard could be clearer topic: canvas labels Jun 26, 2020
Copy link
Contributor Author

@yiyix yiyix left a comment

Choose a reason for hiding this comment

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

@yiyix you need to make your (assumed) membership of https://github.com/googlers public in order for the Participation check to be able to pass.

Thank you so much for the hint, I have added myself there and set it public, Hopefully I will pass the participation check soon. Thank you so much for changing my files! I will look them in details now.

source Outdated Show resolved Hide resolved
source Outdated Show resolved Hide resolved
source Outdated Show resolved Hide resolved
Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

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

LGTM! Will let @annevk merge.

@yiyix
Copy link
Contributor Author

yiyix commented Jun 28, 2020

@jfkthame and I discussed this and found there are concepts defined in CSS Fonts already, which we're now using. I filed w3c/csswg-drafts#5266 to ensure those concepts stick around.

At this point this could use a final round of review from @yiyix / @fserb (given the many changes) and @domenic.

LGTM, Thank you for correcting my grammar errors and thank you for dig into CSS Fonts. It looks better now and i agree with the changes.

@annevk annevk merged commit 93e4504 into whatwg:master Jun 29, 2020
annevk added a commit that referenced this pull request Aug 14, 2020
See w3c/csswg-drafts#5312. And also #5429 for where all of this started.

Ideally though w3c/csswg-drafts#5431 would be fixed too and we'd figure out how to update images/baselines.png (I've asked Ian if there's an original somewhere).
annevk added a commit that referenced this pull request Jun 2, 2021
See w3c/csswg-drafts#5312. And also #5429 for where all of this started.

Ideally though w3c/csswg-drafts#5431 would be fixed too and we'd figure out how to update images/baselines.png (I've asked Ian if there's an original somewhere).
annevk added a commit that referenced this pull request Dec 4, 2024
See w3c/csswg-drafts#5312. And also #5429 for where all of this started.

Ideally though w3c/csswg-drafts#5431 would be fixed too and we'd figure out how to update images/baselines.png (I've asked Ian if there's an original somewhere).
annevk added a commit that referenced this pull request Dec 5, 2024
See w3c/csswg-drafts#5312. And also #5429 for where all of this started.

This should help #6731 quite a bit too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: canvas
Development

Successfully merging this pull request may close these issues.

5 participants