luisherranz
@luisherranz on WordPress.org and Slack
- Member Since: October 6th, 2015
- Location: Madrid
- GitHub: luisherranz
- Job Title: Code Wrangler
- Employer: Automattic
Bio
Contributions Sponsored
Contribution History
luisherranz’s badges:- Core Contributor
- Plugin Developer
- WordCamp Speaker
-
Merged pull request #50953 into WordPress/gutenberg:
Navigation block: Set correct aria-expanded on hover -
Closed issue #50866 on the WordPress/gutenberg repository:
Expose the minimal Interactivity API in a public package -
Created issue #51056 in the WordPress/gutenberg repository:
Tracking Issue: Expose the full Interactivity API in `@wordpress/interactivity` -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
Sadly, solutions like v8js are not backward compatible with all the WordPress instances of the… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
Hey David :) I think we are aligned here. Gutenberg 15.9 will ship a couple… -
Closed issue #49868 on the WordPress/gutenberg repository:
Tracking Issue - Interactivity API runtime for core blocks -
Closed issue #50744 on the WordPress/gutenberg repository:
Submenu closes while focus is on parent link -
Closed issue #50752 on the WordPress/gutenberg repository:
Missing Navigation Submenu Chevron Button Missing `aria-expanded` Attribute on load -
Closed issue #50746 on the WordPress/gutenberg repository:
Can't Close the Submenu with Click or Keypress on Chevron -
Submitted pull request #50953 to WordPress/gutenberg:
Navigation block: Set correct aria-expanded on hover -
Created issue #238 in the WordPress/block-interactivity-experiments repository:
Rename `data-wp-island` to `data-wp-interactive` -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
To do them properly they need to be a progressive enhancement (so that the link… -
Created issue #50866 in the WordPress/gutenberg repository:
Expose the minimal Interactivity API in a public package -
Merged pull request #236 into WordPress/block-interactivity-experiments:
Follow preact logic on enumerated attributes -
Submitted pull request #236 to WordPress/block-interactivity-experiments:
Follow preact logic on enumerated attributes -
Closed issue #152 on the WordPress/block-interactivity-experiments repository:
Remove directive tags (components) from the proposal -
Closed issue #221 on the WordPress/block-interactivity-experiments repository:
Potential JS overhead for URLs or sites that use just 1-2 simple... -
Confirmed as a speaker for WordCamp Europe 2023
-
Closed issue #191 on the WordPress/block-interactivity-experiments repository:
Refs are not passed correctly to directive callbacks -
Merged pull request #224 into WordPress/block-interactivity-experiments:
Fix `evaluate` so it is always the same function instance -
Pull request #225 merged into WordPress/block-interactivity-experiments:
Add wp-init and other small adjustments -
Submitted pull request #225 to WordPress/block-interactivity-experiments:
Add wp-init and other small adjustments -
Pull request #223 merged into WordPress/block-interactivity-experiments:
Remove _wrapped, expose directives and expose full store -
Merged pull request #217 into WordPress/block-interactivity-experiments:
Remove components and everything related to them -
Submitted pull request #223 to WordPress/block-interactivity-experiments:
Remove _wrapped, expose directives and expose full store -
Merged pull request #103 into WordPress/block-interactivity-experiments:
🎨 Switch toVdom from array iteration to createTreeWalker -
Merged pull request #214 into WordPress/block-interactivity-experiments:
Add server side negation operator -
Created issue #49868 in the WordPress/gutenberg repository:
Tracking Issue - Interactivity API runtime for core blocks -
Submitted pull request #214 to WordPress/block-interactivity-experiments:
Add server side negation operator -
Pull request #213 merged into WordPress/block-interactivity-experiments:
wp-bind improvements and negation in runtime -
Submitted pull request #213 to WordPress/block-interactivity-experiments:
wp-bind improvements and negation in runtime -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
For what it's worth, I can relate to your feeling. We've been through a similar… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
That is a great point. Matías suggested the same a few days ago, so we… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
Thanks for these great questions, Weston. I’m trying to understand the utility of effects. We're… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
Alpine.js was the first library that we tested when we started researching the HTML-first approach,… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
could you not do something similar with context by adding a wp_context function or a… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
Hey Joe, thanks for sharing your honest feedback. I understand your point. As you may… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
How would this handle authenticated data? Since this code runs on the frontend of your… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
I wonder if a kind of mandatory namespace to the stores could help with that.… -
Wrote a comment on the post Proposal: The Interactivity API – A better developer experience in building interactive blocks, on the site Make WordPress Core:
If we’re looking at moving interactivity to use these attributes, that means that not only… -
Created issue #202 in the WordPress/block-interactivity-experiments repository:
Router: support hash -
Merged pull request #195 into WordPress/block-interactivity-experiments:
Add `.nvmrc` and `.editorconfig` -
Created issue #198 in the WordPress/block-interactivity-experiments repository:
Helper function for adding data-wp-context in PHP -
Created issue #194 in the WordPress/block-interactivity-experiments repository:
Router: keep favicon when doing client-side navigation -
Created issue #192 in the WordPress/block-interactivity-experiments repository:
Router: cancel navigation when another starts -
Submitted pull request #49305 to WordPress/gutenberg:
Experiment: use the Interactivity API to do client-side form submissions -
Created issue #186 in the WordPress/block-interactivity-experiments repository:
Fallback to server navigation when fetching on the client navigation fails -
Created issue #180 in the WordPress/block-interactivity-experiments repository:
Add `data-wp-key` attribute -
Closed issue #132 on the WordPress/block-interactivity-experiments repository:
Should we follow the HTML specification to the letter? -
Created issue #178 in the WordPress/block-interactivity-experiments repository:
Explore how to integrate the new View Transitions API
Contributor
-
REST API - Head Tags
Active Installs: 500+
