@automattic/jetpack-components 1.12.4 → 1.12.6

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.
Files changed (4) hide show
  1. package/CHANGELOG.md +12 -2
  2. package/build/components/navigator-modal/index.js +16 -5
  3. package/components/navigator-modal/index.tsx +16 -5
  4. package/package.json +13 -13
package/CHANGELOG.md CHANGED
@@ -2,6 +2,14 @@
2
2
 
3
3
  ### This is a list detailing changes for the Jetpack RNA Components package releases.
4
4
 
5
+ ## [1.12.6] - 2026-06-09
6
+ ### Changed
7
+ - Update package dependencies. [#49273]
8
+
9
+ ## [1.12.5] - 2026-06-08
10
+ ### Fixed
11
+ - NavigatorModal: Keep the modal open when the control inside opens an external WP Modal. [#49389]
12
+
5
13
  ## [1.12.4] - 2026-06-08
6
14
  ### Changed
7
15
  - Internal updates.
@@ -12,10 +20,10 @@
12
20
 
13
21
  ## [1.12.2] - 2026-06-02
14
22
  ### Changed
15
- - AdminPage: expand the Hello Dolly normalize rule (was a single `background-color`) to cover the full visual treatment (italic, gray text, white background, right-aligned, hidden under 660px) so individual plugins don't need their own per-page overrides. No position/offsets are set so per-page `position: absolute` overrides (e.g. My Jetpack) keep working. [#48472]
23
+ - AdminPage: Ensure Hello Dolly doesn't require per-page overrides. [#48472]
16
24
 
17
25
  ### Fixed
18
- - Pricing table: render feature tooltips as a portal so they are no longer hidden behind the admin sidebar [#49318]
26
+ - Pricing table: Render feature tooltips as a portal so they are no longer hidden behind the admin sidebar. [#49318]
19
27
 
20
28
  ## [1.12.1] - 2026-06-01
21
29
  ### Changed
@@ -1828,6 +1836,8 @@
1828
1836
  ### Changed
1829
1837
  - Update node version requirement to 14.16.1
1830
1838
 
1839
+ [1.12.6]: https://github.com/Automattic/jetpack-components/compare/1.12.5...1.12.6
1840
+ [1.12.5]: https://github.com/Automattic/jetpack-components/compare/1.12.4...1.12.5
1831
1841
  [1.12.4]: https://github.com/Automattic/jetpack-components/compare/1.12.3...1.12.4
1832
1842
  [1.12.3]: https://github.com/Automattic/jetpack-components/compare/1.12.2...1.12.3
1833
1843
  [1.12.2]: https://github.com/Automattic/jetpack-components/compare/1.12.1...1.12.2
package/build/components/navigator-modal/index.js CHANGED
@@ -16,16 +16,27 @@ function InternalNavigatorModal({ children, className, ...props }) {
16
16
  const { onClose, initialPath } = useContext(NavigatorModalContext);
17
17
  const overlayRef = useRef(null);
18
18
  const isUserInteracting = useRef(false);
19
- // Track pointer interaction on the overlay so we can distinguish
20
- // user-initiated overlay clicks from the WP Modal dismisser mechanism,
21
- // which also calls onRequestClose() without an event argument.
19
+ /*
20
+ * Track pointer interaction on the overlay so we can distinguish
21
+ * user-initiated overlay (backdrop) clicks from the WP Modal dismisser
22
+ * mechanism, which also calls onRequestClose() without an event argument.
23
+ *
24
+ * Only a pointerdown on the overlay element itself counts as a backdrop
25
+ * interaction — mirroring WP Modal's own `event.target === event.currentTarget`
26
+ * check. Without this target guard, a pointerdown on any control inside the
27
+ * modal (e.g. the "Generate image" button) would bubble up and set the flag,
28
+ * so when that control opens an external Modal (Image Studio) the resulting
29
+ * dismisser call would be misread as an overlay click and wrongly close us.
30
+ */
22
31
  useEffect(() => {
23
32
  const overlay = overlayRef.current;
24
33
  if (!overlay) {
25
34
  return;
26
35
  }
27
- const handler = () => {
28
- isUserInteracting.current = true;
36
+ const handler = (event) => {
37
+ if (event.target === overlay) {
38
+ isUserInteracting.current = true;
39
+ }
29
40
  };
30
41
  overlay.addEventListener('pointerdown', handler);
31
42
  return () => overlay.removeEventListener('pointerdown', handler);
package/components/navigator-modal/index.tsx CHANGED
@@ -27,16 +27,27 @@ function InternalNavigatorModal( {
27
27
  const overlayRef = useRef< HTMLDivElement >( null );
28
28
  const isUserInteracting = useRef( false );
29
29
 
30
- // Track pointer interaction on the overlay so we can distinguish
31
- // user-initiated overlay clicks from the WP Modal dismisser mechanism,
32
- // which also calls onRequestClose() without an event argument.
30
+ /*
31
+ * Track pointer interaction on the overlay so we can distinguish
32
+ * user-initiated overlay (backdrop) clicks from the WP Modal dismisser
33
+ * mechanism, which also calls onRequestClose() without an event argument.
34
+ *
35
+ * Only a pointerdown on the overlay element itself counts as a backdrop
36
+ * interaction — mirroring WP Modal's own `event.target === event.currentTarget`
37
+ * check. Without this target guard, a pointerdown on any control inside the
38
+ * modal (e.g. the "Generate image" button) would bubble up and set the flag,
39
+ * so when that control opens an external Modal (Image Studio) the resulting
40
+ * dismisser call would be misread as an overlay click and wrongly close us.
41
+ */
33
42
  useEffect( () => {
34
43
  const overlay = overlayRef.current;
35
44
  if ( ! overlay ) {
36
45
  return;
37
46
  }
38
- const handler = () => {
39
- isUserInteracting.current = true;
47
+ const handler = ( event: PointerEvent ) => {
48
+ if ( event.target === overlay ) {
49
+ isUserInteracting.current = true;
50
+ }
40
51
  };
41
52
  overlay.addEventListener( 'pointerdown', handler );
42
53
  return () => overlay.removeEventListener( 'pointerdown', handler );
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@automattic/jetpack-components",
3
- "version": "1.12.4",
3
+ "version": "1.12.6",
4
4
  "description": "Jetpack Components Package",
5
5
  "homepage": "https://github.com/Automattic/jetpack/tree/HEAD/projects/js-packages/components/#readme",
6
6
  "bugs": {
@@ -73,23 +73,23 @@
73
73
  ],
74
74
  "dependencies": {
75
75
  "@automattic/format-currency": "1.0.1",
76
- "@automattic/jetpack-api": "^1.0.28",
77
- "@automattic/jetpack-boost-score-api": "^1.0.46",
76
+ "@automattic/jetpack-api": "^1.0.29",
77
+ "@automattic/jetpack-boost-score-api": "^1.0.47",
78
78
  "@automattic/jetpack-script-data": "^0.6.4",
79
79
  "@automattic/number-formatters": "^1.2.2",
80
80
  "@babel/runtime": "^7",
81
81
  "@gravatar-com/hovercards": "0.16.0",
82
82
  "@wordpress/admin-ui": "2.1.0",
83
- "@wordpress/browserslist-config": "6.46.0",
84
- "@wordpress/components": "33.1.0",
85
- "@wordpress/compose": "7.46.0",
86
- "@wordpress/data": "10.46.0",
87
- "@wordpress/date": "5.46.0",
88
- "@wordpress/element": "6.46.0",
89
- "@wordpress/i18n": "6.19.0",
83
+ "@wordpress/browserslist-config": "6.48.0",
84
+ "@wordpress/components": "35.0.0",
85
+ "@wordpress/compose": "8.1.0",
86
+ "@wordpress/data": "10.48.0",
87
+ "@wordpress/date": "5.48.0",
88
+ "@wordpress/element": "8.0.0",
89
+ "@wordpress/i18n": "6.21.0",
90
90
  "@wordpress/icons": "13.1.0",
91
- "@wordpress/notices": "5.46.0",
92
- "@wordpress/theme": "0.13.0",
91
+ "@wordpress/notices": "5.48.0",
92
+ "@wordpress/theme": "0.15.0",
93
93
  "@wordpress/ui": "0.13.0",
94
94
  "clsx": "2.1.1",
95
95
  "js-sha256": "0.11.1",
@@ -101,7 +101,7 @@
101
101
  "uplot-react": "1.1.4"
102
102
  },
103
103
  "devDependencies": {
104
- "@automattic/jetpack-base-styles": "^1.2.5",
104
+ "@automattic/jetpack-base-styles": "^1.2.6",
105
105
  "@babel/core": "7.29.0",
106
106
  "@babel/preset-react": "7.28.5",
107
107
  "@jest/globals": "30.4.1",