@financial-times/o-topper 7.1.2 → 7.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Changelog
2
2
 
3
+ ## [7.1.3](https://github.com/Financial-Times/origami/compare/o-topper-v7.1.2...o-topper-v7.1.3) (2026-01-15)
4
+
5
+
6
+ ### Bug Fixes
7
+
8
+ * ci-2860 add padding to avoid overlap ([3c68843](https://github.com/Financial-Times/origami/commit/3c688439c098576e397fbea656769e6fc6502381))
9
+ * ci-2860 add padding to avoid overlap ([95b72ae](https://github.com/Financial-Times/origami/commit/95b72ae1fe05e485c54b371f62ff3194e815bca7))
10
+
3
11
  ## [7.1.2](https://github.com/Financial-Times/origami/compare/o-topper-v7.1.1...o-topper-v7.1.2) (2025-10-28)
4
12
 
5
13
 
package/MIGRATION.md CHANGED
@@ -21,13 +21,12 @@ To upgrade, replace the following "o2" components with their "o3" equivalent:
21
21
 
22
22
  `o-topper` no longer includes JavaScript to select the correct topper for JSON-formatted FT articles and flags. This helper was deeply tied to the FT.com content store, and included hardcoded UUIDs and business logic beyond the scope of Origami. Origami components focus on providing reusable user interfaces – without business logic assumptions which could limit their use outside specific groups or use-cases.
23
23
 
24
- To migrate, replace `o-topper` JavaScript with [`n-map-content-to-topper`](https://github.com/Financial-Times/n-map-content-to-topper).
24
+ Logic for topper selection is now handled in the Topper model in [`cp-content-pipeline`](https://github.com/financial-times/cp-content-pipeline/). The previous library for this, [`n-map-content-to-topper`](https://github.com/Financial-Times/n-map-content-to-topper), is now archived.
25
25
 
26
- ```diff
27
- -import { mapContentToTopper } from '@financial-times/o-topper';
28
- +import mapContentToTopper from '@financial-times/n-map-content-to-topper';
29
- const topper = mapContentToTopper(ftArticle, flags);
30
- ```
26
+
27
+ <del>
28
+ To migrate, replace `o-topper` JavaScript with [`n-map-content-to-topper`](https://github.com/Financial-Times/n-map-content-to-topper).
29
+ </del>
31
30
 
32
31
  ## Migrating from v4 to v5
33
32
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@financial-times/o-topper",
3
- "version": "7.1.2",
3
+ "version": "7.1.3",
4
4
  "description": "Article header styling",
5
5
  "keywords": [
6
6
  "topper",
@@ -46,6 +46,19 @@
46
46
  );
47
47
  }
48
48
  }
49
+ // Add padding to prevent headline text colliding with headshot
50
+ // not needed for opinion toppers as they have a different layout
51
+ // meaning there is no risk of collision and we want the headline
52
+ // to take up all of the available space where possible
53
+ &:not(.o-topper--opinion) {
54
+ .o-topper__headline {
55
+ @include oPrivateGridRespondTo($until: M) {
56
+ padding-right: calc(
57
+ #{$_o-topper-headshot-width} + #{oPrivateSpacingByName('s3')}
58
+ );
59
+ }
60
+ }
61
+ }
49
62
  }
50
63
 
51
64
  @mixin _oTopperThemeOpinion {