IFRAME invalid URL exception HTMX 1.9 to latest

[robmurrer]

If you're HTMX page is inside a iframe. This seems to cause the verifyURL exception in the console.

PR incoming to fix

[robmurrer]

So I guess the flow is to copy dev branch then send PR for code changes. Will do it eventually but for now this is the change:

`/**

• @param {Element} elt
• @param {string} path
• @param {HtmxRequestConfig} requestConfig
• @return {boolean}
  */
  function verifyPath(elt, path, requestConfig) {
  let sameHost
  let url
  if (typeof URL === 'function') {
  if (document.location.href === 'about:srcdoc') {
  sameHost = false
  } else {
  url = new URL(path, document.location.href)
  const origin = document.location.origin
  sameHost = origin === url.origin
  }

} else {
// IE11 doesn't support URL
  url = path
  sameHost = startsWith(path, document.location.origin)
}`

[scrhartley]

Please could you update the description to clarify that this is about iframes using the srcdoc attribute and not about all iframes.

[MichaelWest22]

dev...MichaelWest22:htmx:srcdoc-iframe-origin here is another possible way this could be fixed maybe. When the location protocol is about: the URL() will always fail so we can fall back to using window.origin which in the iframe case like srcdoc ones it will normally have the real origin in window.origin we can use. I was unable to find any way currently to find the current actual full href in this situation but origin base is all that is needed here really. With this fix the sameHost check works as expected as well.

    if (typeof URL === 'function') {
      url = new URL(path, document.location.protocol !== 'about:' ? document.location.href : window.origin)
      const origin = document.location.protocol !== 'about:' ? document.location.origin : window.origin
      sameHost = origin === url.origin
    } else {

This problem only seems to happen with srcdoc iframes and I'm unsure if this is a good way to use htmx inside iframes where the contents of the iframe is generated inside the main page dynamically and then this content then gets updated via htmx inside the iframe which will then not match the original srcdoc of the iframe.

[MichaelWest22]

This should be fixed now in 2.0.5