SYMPTOM
On a Tableau Server dashboard with two data-blended data sources and a filter
action that passes the blend linking field from a source viz to a target viz,
the action-highlight indicator on the source viz turns on and off (flickers)
when the user clicks or drags in the empty space inside the target viz's frame
(not on a mark). The flicker occurs in a web browser only; the same workbook
opened in Tableau Desktop does not flicker. Reported across multiple viz types,
not limited to maps.
CAUSE
The flicker originates in the browser's client-side rendering (CSR) path. On
the same interaction, CSR and server-side rendering (SSR) fire different
selection actions: CSR fires "select region, no return server" while SSR fires
"select none". The CSR selection action repaints the source viz's highlight
state repeatedly, producing the flicker. CSR is the default render path for
views under the complexity threshold, so a simple blended workbook engages CSR
automatically. Because the render path, not the product version, is the
differentiator, the behavior is longstanding rather than a version-specific
regression. A workbook can appear to begin flickering after an upgrade if
growing complexity pushes it across the CSR/SSR threshold and flips its render
path.
WORKAROUND
Force server-side rendering for the affected view to stop the flicker:
1. Per view (lightweight, session-scoped): append :render=false to the view
URL. Example: https://<server>/#/views/<workbook>/<view>?:render=false
2. Server-wide (heavier, has a performance tradeoff, not the first choice):
tsm configuration set -k vizqlserver.browser.render -v false
Reference: https://help.tableau.com/current/server/en-us/browser_rendering.htm
The workaround is not universal. On some blended workbooks :render=false does
not stop the flicker. This occurs when the view is not eligible for client-side
rendering in the first place (certain viz types cannot render client-side, and
views above the CSR mark threshold render server-side regardless), so forcing
:render=false is a no-op there. Tableau Desktop (native renderer, never the
browser CSR path) is not affected and can be used as a comparison baseline.
005390353

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.