… the iframe window's onload addressed this.
…ource downloading by the prescanner.
…ging document URL is same as `document.URL`.
…pturing and decor document also had <title>.
…set needs the same override.
Now normalize() and deneutralizeAll() are called as part of Capture.getDocument() instead of in decor.start(). This is the same as what happens for panned pages.
- script@src must always resolve - img@srcset and a@ping need special resolveURL code
…empty cache script.onreadystatechange handlers weren't being called. Wrapping enableScript() in setTimeout() resolved this issue. Not sure why.
attrDesc.deref is merged with attrDesc.neutralize. If `neutralize` is true then the attribute needs to be neutralized before parsing. If `neutralize` is `> 0` then the attribute stays neutralized during the normalize() call. This means that if `neutralize` is less-than-zero the attribute will be neutralized for parsing and deneutralized for normalizing.
… rather than prepending the attribute *name* with "meeko-". This allows picture polyfill to work in the normalize(doc) call as it copies `source@src` to `img@src`. Also, if STAGING_DOCUMENT_IS_NEUTRAL then don't even need to keep neutralized URLs around for the normalize() call. See resolveAll() and deneutralizeAll().
…audio>. Needed if <picture> becomes best-practice.
panner.navigate() now calls location.assign() (or replace() ) if history.pushState() not available.
…ing the <head> into an iframe and using element.innerHTML for the <body>. Can't hurt perf on other browsers. Also use DOMParser.parseFromString(html, 'text/html') on browsers that support it - that is, Firefox.
HTMLParser adds `style="display: none"` to <body>. This usually makes parsing a bit faster on IE8. The mergeElement() mod means this doesn't affect final view.
Add `mustResolve` field to `details` object that is passed to HTMLLoader and HTMLParser Resolving URLs in the landing-page now runs over everything in <head>, not just elements after the self-marker
…nner bookmarklet highlighted this bug.
…> when boot-script isn't in the head (as occurs in meeko-panner bookmarklet)
and capturing + long.html highlighted this bug.
…e in script
Implement resolveAll(doc, baseURL, isNeutralized) to be called from HTMLParser and HTMLLoader where appropriate. Not all URL attrs in the landing-page need to be resolved, because most elements will be paged out anyway when panning. For now just resolve script@src and link@href in <head>