Bug 181503 - Negative text-indent on inline-block won't reduce width fully when multiple counters present
Summary: Negative text-indent on inline-block won't reduce width fully when multiple c...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2018-01-10 15:41 PST by Roman Komarov
Modified: 2022-08-20 16:17 PDT (History)
7 users (show)

See Also:


Attachments
STP 151 matches with all other browsers but differ from Safari 15.6.1 (1.89 MB, image/png)
2022-08-20 16:16 PDT, Ahmad Saleem
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Komarov 2018-01-10 15:41:21 PST
## Steps to reproduce the problem:

Go to https://codepen.io/kizu/pen/ZvxMoz

or

1. Create an element with width fitted to content (like inline-block)
2. Add pseudo with content containing multiple CSS counters (more than 1)
3. Add negative text-indent that would cover the width of all added symbols.

## What is the expected behavior?

The element's width should be equal to zero

## What went wrong?

The element's width would be equal to the number of counters minus one in characters (really strange)


Other browsers: Firefox and Edge render this properly.
Comment 1 Roman Komarov 2019-06-21 03:21:10 PDT
Wanted to post an update: this was fixed in Chromium, so Safari would become the only one still having this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=800985
Comment 2 Radar WebKit Bug Importer 2019-06-22 12:55:20 PDT
<rdar://problem/52022022>
Comment 3 Ahmad Saleem 2022-08-20 16:16:39 PDT
Created attachment 461773 [details]
STP 151 matches with all other browsers but differ from Safari 15.6.1

I am able to reproduce this bug using CodePen from Comment 0 in Safari 15.6.1 but not in Safari Technology Preview 151, which matches with other browsers (Chrome Canary 106 and Firefox Nightly 105).

I am going to mark this as "RESOLVED CONFIGURATION CHANGED", please reopen if I am testing incorrectly. Thanks!