Changes between Version 1 and Version 2 of Ticket #42201, comment 52
- Timestamp:
- 10/16/2019 11:34:34 PM (10 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #42201, comment 52
v1 v2 5 5 If I am reading this correctly, anything now "inside" that now-flexed anchor is forced to be a flex element. 6 6 7 Using `display: block !important;` even gets ignored in all browsers, confirming (to me) that child pseudo elements of a flexed element are forced to flex, meaning there is no alternative CSS to get this styling working again .7 Using `display: block !important;` even gets ignored in all browsers, confirming (to me) that child pseudo elements of a flexed element are forced to flex, meaning there is no alternative CSS to get this styling working again (a more strict hack could override the core anchor styling, but whack-a-mole priority juggling isn't a solution IMO.) 8 8 9 9 > A flex item establishes an independent formatting context for its contents. However, flex items themselves are flex-level boxes, not block-level boxes: they participate in their container’s flex formatting context, not in a block formatting context.