Latest / Wpfavs - Your favourite WordPress news / WordPress 7.1: WebAssembly, Iframes, and AI APIs

Transcript

WordPress 7.1: WebAssembly, Iframes, and AI APIs · Wpfavs - Your favourite WordPress news

• 0:13
  So, August 19th in Phoenix at WordCamp US, WordPress 7.1 lands,
• 0:18
  and, uh, look, the headline everyone is gonna talk about is the WebAssembly stuff.
• 0:22
  It literally handles image compression, resizing, format conversion,
• 0:27
  rotation, and thumbnail generation directly in the user's browser using WebAssembly.
• 0:32
  That bypasses server PHP memory limits completely when uploading giant client
• 0:37
  photos.
• 0:38
  Wait, wait, it, it runs all of that in the browser?
• 0:40
  Like, entirely on the client side before it even hits the server?
• 0:43
  Yeah!
• 0:44
  Exactly.
• 0:45
  But, um, while everyone is celebrating zero server timeouts on five megapixel
• 0:50
  uploads, the full editor iframe isolation is reaching 100 percent coverage.
• 0:55
  Every legacy meta box is sandboxed now.
• 0:58
  No more CSS leaking into the editor.
• 1:01
  But if you have older plugins doing direct parent DOM traversal using window point
• 1:05
  parent, boom, totally broken.
• 1:07
  Okay, I, I gotta call flag on that.
• 1:10
  The DOM iframe break is gonna cause a hundred times more emergency support tickets
• 1:14
  on launch day than WebAssembly!
• 1:16
  Agency builders have custom meta boxes from 2018 that rely on window point parent.
• 1:22
  When those silently fail on August 19th, client dashboards are just gonna freeze.
• 1:26
  I, I actually think you are both missing the bigger architectural shift here.
• 1:31
  The iframe work is just housing cleanup.
• 1:34
  Look at the developer APIs!
• 1:36
  We get a standardized SVG Icon API, sure, but more importantly,
• 1:41
  the Abilities API now has JSON Schema filtering and lifecycle execution hooks right
• 1:48
  inside wp get abilities.
• 1:50
  They are literally turning core WordPress functions into structured tools for AI
• 1:55
  agents!
• 1:56
  Right!
• 1:56
  Because an AI assistant like Claude or ChatGPT needs structured,
• 2:00
  typed schemas to know what a function accepts before it executes PHP or queries the
• 2:04
  database.
• 2:05
  That makes the entire site readable and executable for external agents!
• 2:09
  I get the AI excitement, I do, but Ben, back to your point about support tickets,
• 2:14
  WebAssembly is running raw client side code across thousands of different device
• 2:18
  browsers.
• 2:19
  Old Android phones, weird Safari desktop edge cases trying to do WebAssembly image
• 2:25
  rotation on a ten megabyte image?
• 2:27
  That memory crash happens in the client browser where developers can't even see the
• 2:32
  error log!
• 2:33
  That is a support nightmare.
• 2:34
  No way, Nick.
• 2:35
  Browsers throw clear WebAssembly errors.
• 2:38
  Broken legacy scripts trying to reach parent document elements from inside an
• 2:41
  isolated iframe fail silently.
• 2:44
  A client clicks save, nothing happens, and they blame the host or the developer.
• 2:48
  Well, before we panic about launch day bugs, we should talk about what actually got
• 2:53
  left on the cutting room floor for 7.1.
• 2:56
  Real time collaborative editing, the whole Google Docs style co editing inside
• 3:02
  Gutenberg, pulled late after cycle testing.
• 3:06
  And the React 19 core upgrade?
• 3:08
  Deferred back to experimental Gutenberg plugin builds.
• 3:11
  Honestly, um, as someone who manages dozens of live client environments,
• 3:16
  pulling collaborative editing was the smartest move core team made.
• 3:20
  Real time state sync across database locks was nowhere near ready.
• 3:24
  Can you imagine database bloat from constant auto drafts?
• 3:28
  It is smart for stability, yes, but think about the strategic message for WordCamp
• 3:32
  US in Phoenix.
• 3:34
  Pulling human co editing while doubling down on the Abilities API and Novamira style
• 3:38
  agent execution hooks?
• 3:40
  Core isn't prioritizing two human editors typing in the same block at the same time.
• 3:45
  They are building for a human and an AI agent co editing the site behind the scenes.
• 3:49
  That is a massive point, Ido.
• 3:51
  Autonomous site administration needs reliable schema boundaries,
• 3:54
  not multi user DOM cursors.
• 3:56
  That is where the entire ecosystem is going.
• 3:59
  Okay, fair, but before we ascend into autonomous AI futures,
• 4:03
  agencies need a concrete pre upgrade sanity checklist for August 19th.
• 4:09
  First, test your persistent top toolbar behavior across custom admin themes.
• 4:13
  Second, audit all legacy theme scripts against jQuery UI 1.14.2.
• 4:19
  If your scripts call deprecated jQuery UI functions, 7.1 will drop them.
• 4:24
  So what is your personal takeaway, Nick?
• 4:26
  Are you relieved or terrified for this deploy?
• 4:29
  A bit of both!
• 4:30
  I am genuinely relieved real time editing was cut so my database stays clean,
• 4:34
  but my biggest remaining concern is still that iframe isolation.
• 4:39
  If you have custom client sites built over the last five years,
• 4:42
  test 7.1 Beta 4 on staging today, or August 19th in Phoenix is going to be a very
• 4:48
  long day.
• 4:49
  Staging tests today, AI agent schemas tomorrow.
• 4:52
  Sounds like a classic WordPress release cycle to me.