Tableau Cloud Web Authoring is a TWO-STEP transition — canvas DOM at TOP-LEVEL,
Tableau Cloud Web Authoring is a TWO-STEP transition — canvas DOM at TOP-LEVEL, not iframe
Confirmed live 2026-04-25 against Tableau Cloud 2026.1.1, Runwal site.
The actual flow (NOT what pattern-extrapolation suggests):
- Navigate
/views/<contentUrl>/<sheet>?:edit=y— page loads with viewer iframeiframe[title='Data Visualization'](viewer toolbar) - Inside that iframe, click
[data-tb-test-id='viz-viewer-toolbar-button-edit'] - TOP-LEVEL page transitions to
/authoring/<contentUrl>/<sheet>— iframe goesabout:blank - Actual authoring DOM lives at TOP-LEVEL:
VisualizationContainer,*-ToolbarButton,tab*ZoneObject,authMenuBarPublishButtonMainPart-Button
URL gotchas
/views/<contentUrl>/sheets?:edit=yrejected — needs real sheet name (resolve viaWorkbooks.populate_views(wb)+wb.views[0].content_url)- Tableau Cloud routes use
/workbooks/<NUMERIC>(fromwb.webpage_url), NOT LUID
tableauserverclient API
get_revisions(wb)doesn’t exist — usepopulate_revisions(wb)thenwb.revisions
Calc dialog requires worksheet
Right-click data pane → Create Calculated Field works on WORKSHEETS only, not dashboards.
Reference
/opt/clis/cli-anything/tableau-cloud-author/.../core/page.py:enter_authoring_frame() — 7/7 critical selectors verified live.