Skip to content

Conversation

@gitspeaks
Copy link
Contributor

In this context, 'the original containing block' is the 'absolute-position containing block'

@gitspeaks gitspeaks changed the title link to absolute-position containing block [css-position-3] link to absolute-position containing block Nov 19, 2024
@w3cbot
Copy link

w3cbot commented Nov 19, 2024

svgeesus marked as non substantive for IPR from ash-nazg.

Copy link
Contributor

@Loirooriol Loirooriol left a comment

Choose a reason for hiding this comment

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

Why are you changing CSS2 in a PR that says [css-position-3]?

AFAIK CSS2 is in a state where we are not sure what changes have happened since REC, and further divergence would make things messier.

Better stick to CSS Position.

@gitspeaks
Copy link
Contributor Author

Why are you changing CSS2 in a PR that says [css-position-3]?

AFAIK CSS2 is in a state where we are not sure what changes have happened since REC, and further divergence would make things messier.

Better stick to CSS Position.

This was not intentional. I thought GitHub would prompt me. How can I now exclude the CSS2 changes from the pull request?

@Loirooriol
Copy link
Contributor

Reset your branch to the right commit and force-push it.

@gitspeaks
Copy link
Contributor Author

Reset your branch to the right commit and force-push it.

Done.

@gitspeaks
Copy link
Contributor Author

AFAIK CSS2 is in a state where we are not sure what changes have happened since REC, and further divergence would make things messier.
Better stick to CSS Position.

The CSS2 section contains relevant information not present in the CSS Position section

Copy link
Contributor

@Loirooriol Loirooriol left a comment

Choose a reason for hiding this comment

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

There are two concepts:

It seems like the spec was trying to link to the former one. However, testcase:

<!DOCTYPE html>
<div style="display: inline-grid; grid-template: 50px 50px 50px / 50px 50px 50px; border: solid; position: relative">
  <div style="grid-area: 2 / 2 / 3 / 3; background: cyan; position: absolute; width: 100%; height: 100%"></div>
</div>

The percentages resolve to the grid area in Gecko, Blink and WebKit, so it's not the "original containing block".

So the edit seems good but it has behavior implications. Then I think it becomes substantive for IPR, and requires approval by editor discretion or CSSWG.

Copy link
Contributor

@Loirooriol Loirooriol left a comment

Choose a reason for hiding this comment

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

OK, so some archeology:

Therefore, despite using the same words, it wasn't referring to the original containing block. Then I think this PR isn't affecting conformance after all.

But better let the editors confirm, I guess.

@gitspeaks
Copy link
Contributor Author

gitspeaks commented Nov 22, 2024

At the time of submission, I was not aware of the term "original containing block" as defined in the specification. I'm not saying the term did not exist; I simply did not consider looking up [=containing block=], as I assumed I already understood what 'containing block' means.

My interpretation of the wording "original containing block" was that it referred to the containing block from which the 'inset-modified containing block' was derived. The use of the word 'however' suggested this interpretation to me, emphasizing that percentage calculations are not performed against the 'inset-modified containing block' but rather the box serving as the reference from which the offsets of the 'inset-modified containing block' were calculated.

I inferred this interpretation directly from the definition in section 3.5:

"For an absolutely positioned box, the inset properties effectively reduce the containing block into which it is sized and positioned by the specified amounts. The resulting rectangle is called the inset-modified containing block. (For disambiguation, the actual containing block of an absolutely positioned box can also be called the absolute-position containing block.)"

My understanding was that "actual containing block" is equivalent to "original containing block."

This is why, in the pull request message, I wrote: "In this context, 'the original containing block' is the 'absolute-position containing block.'"

@gitspeaks
Copy link
Contributor Author

I am submitting the pull request under the CC0 license.

@fantasai fantasai merged commit 77bb735 into w3c:main Nov 5, 2025
1 check passed
@fantasai
Copy link
Collaborator

fantasai commented Nov 5, 2025

Thanks @gitspeaks and @Loirooriol for catching this.

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

Successfully merging this pull request may close these issues.

5 participants