Bug 1700858 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

The latest resolution https://github.com/w3c/csswg-drafts/issues/129#issuecomment-893052191

> RESOLVED: Undo previous resolution. Explicitly mark as undefined in the draft for now

From Ian in the meting:  

> <dael> iank_: What I'm going to do next is change behavior to include inline end padding if it was scrollable and I'll add another use counter for the case I was more worried about. I'll report back in a couple months

So blink is going to investigating whether adding inline-end padding universally in the block container will break websites. Let's reopen this bug to keep tracking undefined behavior.
The latest resolution https://github.com/w3c/csswg-drafts/issues/129#issuecomment-893052191

> RESOLVED: Undo previous resolution. Explicitly mark as undefined in the draft for now

From Ian in the meting:  

> <dael> iank_: What I'm going to do next is change behavior to include inline end padding if it was scrollable and I'll add another use counter for the case I was more worried about. I'll report back in a couple months

So blink is going to investigating whether adding inline-end padding universally in the block container will break websites. Let's reopen this bug to keep tracking this undefined behavior.
The latest resolution https://github.com/w3c/csswg-drafts/issues/129#issuecomment-893052191

> RESOLVED: Undo previous resolution. Explicitly mark as undefined in the draft for now

From Ian in the meeting:  

> <dael> iank_: What I'm going to do next is change behavior to include inline end padding if it was scrollable and I'll add another use counter for the case I was more worried about. I'll report back in a couple months

So blink is going to investigating whether adding inline-end padding universally in the block container will break websites. Let's reopen this bug to keep tracking this undefined behavior.
The latest resolution https://github.com/w3c/csswg-drafts/issues/129#issuecomment-893052191

> RESOLVED: Undo previous resolution. Explicitly mark as undefined in the draft for now

From Ian in the meeting:  

> <dael> iank_: What I'm going to do next is change behavior to include inline end padding if it was scrollable and I'll add another use counter for the case I was more worried about. I'll report back in a couple months

So blink is going to investigating whether adding inline-end padding universally to the block container's overflow area will break websites. Let's reopen this bug to keep tracking this undefined behavior in the spec.

Back to Bug 1700858 Comment 4