New issue
Advanced search Search tips

Issue 883574 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Wrong static position for out-of-flow positioned element with different writing-mode than its containing block

Project Member Reported by obru...@igalia.com, Sep 13

Issue description

Chrome Version: (copy from 68.0.3440.106)
OS: Lubuntu 18.04

What steps will reproduce the problem?

Run this code: http://jsfiddle.net/4pqcexn5/

```css
#container {
  position: relative;
  border: 5px solid;
  padding-left: 100px;
}
#container > * {
  writing-mode: vertical-lr;
}
#abspos {
  position: absolute;
}
```
```html
<div id="container">
  <div id="abspos">abspos</div>
  <div id="static">static</div>
</div>
```

What is the expected result?

The abspos element has all 'top', 'left', 'bottom' and 'right' properties set to 'auto', so it should appear at the static position.
That is, the text 'abspos' should overlap 'static'.

What happens instead?

Instead of being shifted 100px to the right due to padding-left, it's shifted 100px downwards.
This happens when an absolutely (or fixed) positioned element has a different writing mode than its containing block.

WebKit is also affected (https://bugs.webkit.org/show_bug.cgi?id=189513), Firefox does it right.

 
Cc: kojii@chromium.org
Components: -Blink>CSS Blink>Layout
Status: Available (was: Untriaged)
Labels: Fixed-In-LayoutNG

Sign in to add a comment