User Profile
DanielTakeda
New Member
Joined 9 months ago
User Widgets
Contributions
Power BI Service on macOS shows reduced right‑click context menu (no Drill through)
TL;DR: Right‑click on visuals in Power BI Service shows different tooltip menu (Share, Add alert, Show as table) on visuals on PBI service on macOS (no Drill through) compared to Windows, even though all right‑click events fire correctly. I found OS/browser‑specific UI classes in the Power BI client (.mac, .win, .edge, .chrome, etc.), and mac‑specific headers. Even after spoofing Windows user agent, Power BI continues treating macOS as a reduced‑capability environment. This suggests client-level OS gating beyond UA detection. What started the investigation One of our user complained that right clicking on a Country on Azure maps in my PBI report doesn't show him drill trough option. User is on MacOs, presumably Tahoe. I recently also swapped my Windows laptop for MacBook Pro and I get consistently same behavior. In Power BI service at https://app.powerbi.com/: On Windows, right‑clicking a visual in Power BI Service shows full options of 11 entries including Drill through. On macOS, the same report only shows a truncated context menu limited to 3 options. I wanted to know if macOS was blocking right‑click events, or if Power BI was intentionally limiting features. Step 1 — Verified the raw event chain (macOS ≠ the problem) I logged all relevant pointer/mouse/context events with JS. macOS Edge output: pointerdown button=2 … mousedown button=2 … contextmenu button=2 … pointerup button=2 … mouseup button=2 … auxclick button=2 … Windows VM Edge output: pointerdown button=2 … mousedown button=2 … pointerup button=2 … mouseup button=2 … auxclick button=2 … contextmenu button=2 … Conclusion: MacOS browsers are NOT suppressing right‑click and Power BI receives identical right‑click event streams on both platforms. So the missing menu entries are not due to macOS input handling. Step 2 — Found OS/browser detection code in Power BI’s client bundles Searching through minified sources revealed: function Vt(text) { t.classList.add("tooltiptext"); if (navigator.userAgent.indexOf("Edg") !== -1) t.classList.add("edge"); else if (navigator.userAgent.indexOf("Chrome") !== -1) t.classList.add("chrome"); else if (navigator.userAgent.indexOf("Safari") !== -1) t.classList.add("safari"); else if (navigator.userAgent.indexOf("Firefox") !== -1) t.classList.add("firefox"); if (navigator.userAgent.indexOf("Windows") !== -1) t.classList.add("win"); else if (navigator.userAgent.indexOf("Macintosh") !== -1) t.classList.add("mac"); } And OS‑specific CSS: MAC: .atlas-map .tooltiptext.mac { border: .3px ButtonText solid; border-radius: 1px; padding: 0 6px; font-size: .86em; } Windows: .atlas-map .tooltiptext.win.firefox { border: none; border-radius: 2px; } To check if this gating was just UA‑based, I spoofed Windows + Firefox UA and reloaded Power BI. Result was that reduced menu still appears. This implies Power BI uses either OS‑level properties (e.g., navigator.platform, GPU profiles, pointer API availability) and/or capability matrix where certain interaction features are disabled for macOS browsers and/or Hardcoded environment flags that only enable full context menus on Windows. Is this an intentional product decision (macOS considered lower‑capability)? Are there known limitations that restrict right‑click Drillthrough on macOS? Is there a roadmap for bringing the macOS context menu to parity with Windows? If anyone else can reproduce this, please add your results — the more data points we gather, the easier it is to escalate.665Views3likes3Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.