iAPI: Deprecate data-wp-ignore #70881

Activity

1. DAreRodz

   added

   [Type] EnhancementA suggestion for improvement.A suggestion for improvement.

   [Feature] Interactivity APIAPI to add frontend interactivity to blocks.API to add frontend interactivity to blocks.

   [Package] Interactivity/packages/interactivity/packages/interactivity

   on Jul 23, 2025
2. Sahil1617 commented on Jul 23, 2025

   

   Sahil1617

   on Jul 23, 2025

   Contributor

   More actions

   Hi @DAreRodz 👋

   Thanks for highlighting this cleanup opportunity.

   To start, I plan to:

   • Locate where data-wp-ignore is currently being processed.
   • Add a console warning to inform developers that this directive is deprecated.
   • Maintain backward compatibility for now (as suggested), and prepare for its full removal in a future release.

   Let me know if that sounds good or if there are any additional considerations I should be aware of. Looking forward to contributing!
3. DAreRodz commented on Jul 28, 2025

   

   DAreRodz

   on Jul 28, 2025

   ContributorAuthor

   More actions

   Hi, @Sahil1617. 👋 If you're willing to work on this issue, the data-wp-ignore implementation is in the /packages/interactivity/src/directives.tsx file.

   gutenberg/packages/interactivity/src/directives.tsx

   Lines 592 to 610 in 166bc58

   	// data-wp-ignore
   	directive(
   	'ignore',
   	( {
   	element: {
   	type: Type,
   	props: { innerHTML, ...rest },
   	},
   	}: {
   	element: any;
   	} ) => {
   	// Preserve the initial inner HTML.
   	const cached = useMemo( () => innerHTML, [] );
   	return createElement( Type, {
   	dangerouslySetInnerHTML: { __html: cached },
   	...rest,
   	} );
   	}
   	);

   You can use the warn function, like the data-wp-context directive does, to show a deprecation message to developers:

   gutenberg/packages/interactivity/src/directives.tsx

   Lines 229 to 233 in 166bc58

   	if ( ! isPlainObject( value ) ) {
   	warn(
   	`The value of data-wp-context in "${ namespace }" store must be a valid stringified JSON object.`
   	);
   	}
4. Sahil1617 commented on Jul 28, 2025

   

   Sahil1617

   on Jul 28, 2025

   Contributor

   More actions

   Thanks for the pointer, @DAreRodz! 🙌

   I've located the data-wp-ignore directive in /packages/interactivity/src/directives.tsx (lines 592–610), and I plan to:

   1. Add a warn() call within the directive to notify developers that data-wp-ignore is deprecated.
   2. Keep the existing functionality intact for now to ensure backward compatibility.
   3. Add a comment indicating that this directive is scheduled for removal in a future release (e.g., WordPress 6.10 or later).

   I'll open a PR shortly with the changes. Please let me know if you'd prefer any adjustments to the messaging or approach.

   Looking forward to contributing! 🚀
5. DAreRodz

   closed this as completedin #70945on Jul 29, 2025
6. sirreal commented on Aug 27, 2025

   

   sirreal

   on Aug 27, 2025

   Member

   More actions

   Are there alternatives to the ignore directive? I saw the deprecation message recently, but it's unclear whether I can do anything about it or where to go for more information. A link to some explanation in the deprecation message would be nice.
7. emeaguiar commented on Mar 12, 2026

   

   emeaguiar

   on Mar 12, 2026

   Last edited by emeaguiar

   More actions

   +1 on alternatives? A third part script was adding an onClick to the markup on one site, this triggered an error in the interactivity api and data-wp-ignore fixes it, is there a way to get around this now?
8. luisherranz commented on Mar 13, 2026

   

   luisherranz

   on Mar 13, 2026

   Member

   More actions

   Can you give a more concrete example of the HTML and what is failing?