Hi everyone,
I’m migrating a database app to the New Record Experience and I’ve hit what looks like a regression in the HTML rendering of calculation fields: any <iframe> in the calculation output disappears. It renders correctly in the classic record.
Setup:
New record experience enabled for that app + Calculation fields with output type None (untyped) returning HTML. No JavaScript involved — I’m aware that inline JS such as onclick is intentionally not supported, and I’m not using it.
What I see (same app, same record, both layouts):
Feature
Classic record
New Record
<div> + flex + <span> + inline styles
✔ renders
✔ renders
<svg> + inline styles
✔ renders
✔ renders
<a href="…"> wrapping content
✔ renders
✔ renders
<iframe src="https://share.tapeapp.com/…"> (a Tape share link)
✔ renders
✘ nothing
<iframe src="data:text/html;charset=utf-8,…">
✔ renders
✘ nothing, but the block still reserves the iframe's 500px of height
Two things I find telling:
The reserved height suggests the <iframe> element is still being inserted into the DOM, so this doesn’t look like the HTML sanitizer dropping the tag — it looks like the frame is never allowed to load (a framing restriction on the rendering context of the new layout, e.g. a CSP frame-src / sandbox block).The first iframe points at tapeapp.com’s own share domain. So this isn’t a third-party site refusing to be framed — the new layout doesn’t frame Tape’s own page either (I tried to confirm it from the DevTools console, but I couldn’t capture a definitive message).
Minimal reproduction — two calculation fields, output type "None":
// 1) iframe with an https URL: renders in classic, nothing in the new record experience<iframe src="[https://share.tapeapp.com/<YOUR_SHARE_ID>?prefill.single_line_text=${Record_ID}"](https://share.tapeapp.com/%3CYOUR_SHARE_ID%3E?prefill.single_line_text=%24%7BRecord_ID%7D%22) width="100%" height="600px"></iframe>
// 2) iframe with a data: URL: same behaviour<iframe src="data:text/html;charset=utf-8,%3Ch1%3EHello%3C%2Fh1%3E" width="100%" height="300px"></iframe>
Why it matters to me:
Embedding via <iframe> is a well-established pattern in this community (Tape share links and forms, Fillout/Jotform forms, maps, external dashboards, mini-apps). Most of those threads predate the new record experience, and I have several fields per app relying on it — so right now this is what stops me from moving apps to the new layout. For instance I have a some “embedded” Tape forms I need to use (and can’t if I change).
Questions:
Is <iframe> intentionally not rendered in the New Record Experience, or is it a regression?
If it’s intentional:
What is the supported way to embed external content (or a Tape share link) in a calculation field in the new layout?
If it's a regression:
Is it the same family as the recent inline SVG issue Tim confirmed and fixed?
@R.J thanks for the detailed report, and @Luis thanks for chiming in.
Indeed, that was a regression in the modern calculation field UI being to restrictive in its rendering engine. We just shipped a fix, after a refresh this should work as it used to and as expected.
Hi guys,
Thank you very much both @Luis and @Tim. I’m sorry I couldn’t test this and get back here before.
Regarding the tests I made please find here the results. I am afraid this might be only partially solved but still blocking from changing to the New Record Layout some Apps.
Environment
Same app duplicated: one copy in Classic Record Layout, one in the New Record Layout.
Same calculation field, same script, same input data.
Output type: Text. The API reports return_type: "text"; the UI shows this setting as None in the Output type dropdown — worth noting, since the docs say the output type must be “Text”.
data: and srcdoc are removed before rendering. The blocks reserve no height: the labels above and below sit flush against each other. Compare with the pre-fix behaviour, where the iframe was inserted but never loaded and therefore still reserved its 500px. Here the element is gone.
Non-Tape https is created but not allowed to load. The block reserves its full height and shows the browser’s blocked-frame icon. That might be the signature of a frame-src allowlist, not of a sanitizer.
The same split appears with images: a Tape attachment renders, a non-Tape image leaves a broken-image icon.
It isn’t the calculation. Read through the API, the computed value is complete and correct: 21,045 characters containing the data: iframe with all its signed attachment URLs — structurally identical to the value that renders fine in the classic layout. The data is right; only the rendering differs.
Minimal reproduction.
One calculation field, output type Text, classic editor:
(function(){
var enc = encodeURIComponent;
var L = function(t){ return "<div style='padding:4px 8px;background:#111;color:#fff'>" + t + "</div>"; };
var D = function(h){ return "<iframe src='data:text/html;charset=utf-8," + enc(h) + "' width='100%' height='80'></iframe>"; };
var out = "";
out += L("1 iframe https, Tape domain") + "<iframe src='https://share.tapeapp.com/<share-id>' width='100%' height='80'></iframe>";
out += L("2 iframe https, non-Tape domain") + "<iframe src='https://example.com' width='100%' height='80'></iframe>";
out += L("3 iframe data:, no script") + D("<body style='background:#c62828;color:#fff'>3</body>");
out += L("4 iframe data:, with script") + D("<body style='background:#1565c0;color:#fff'><div id='o'>4 blocked</div><scr"+"ipt>document.getElementById('o').textContent='4 ok';</scr"+"ipt></body>");
out += L("5 iframe srcdoc") + "<iframe srcdoc='<body style="background:#2e7d32;color:#fff">5</body>' width='100%' height='80'></iframe>";
out += L("6 iframe data:, ~21k payload") + D("<body style='background:#6a1b9a;color:#fff'>6</body><!--" + new Array(21000).join("A") + "-->");
out += L("7 img, Tape attachment") + "<img src='https://s3.<region>.amazonaws.com/tape-attachments/<id>?X-Amz-...' style='height:80px'>";
out += L("8 img, non-Tape domain") + "<img src='https://upload.wikimedia.org/wikipedia/commons/4/47/PNG_transparency_demonstration_1.png' style='height:80px'>";
return out;
})()
In the New layout: 1 and 7 render; 2 leaves an empty 80px box with the blocked-frame icon; 3, 4, 5 and 6 leave no gap at all; 8 shows a broken-image icon. In the classic layout all eight render.
Questions
Are the data:/srcdoc removals intentional, or part of the same regression fixed on Nov 1 for the Tape-domain case?
Is the frame-src restriction to Tape origins intentional? If so: could it be relaxed to allow https: generally, or a configurable allowlist of origins per workspace? That alone would unblock the hosted-page pattern (a page we host, fed with the record’s data) without re-enabling data:, which I understand is an XSS vector. It seems like the cheapest way out of this.
Is img-src restricted to Tape origins for the same reason, or is that a separate policy?
If none of the above is considered: what is the supported way to render per-record interactive HTML — own <style> + <script>, values from other fields — in a calculation field in the new record layout? We haven’t found one.
Many thanks @Tim for taking the time to study this and to the team for your fix.