. * Site-wide theme/Elementor styles bleed into that box, and 2.0.12's admin.css * ships frontend-only rules that change what 1.32 did. Every rule below is * scoped to that wrapper or to the Element Plus overlays FB teleports to * (.el-overlay dialogs/drawers, .el-popper popovers), so nothing leaks * to the rest of the site, to wp-admin, or to the Pro standalone portal * (which lacks .fbs_page_render). * * Cascade: this sheet is printed in BEFORE the plugin CSS (ours is * enqueued on wp_enqueue_scripts, FB's during shortcode render), so each * override has to win on specificity, never on order. No !important needed. * FB 2.0 keeps its Element Plus base styles in @layer element-plus; unlayered * theme/Elementor rules beat that layer whatever their specificity, which is * where most of the bleed below comes from. */ /* 1. Black button outline. The theme's global button border (Elementor primary #2e2e2e) lands on Element-Plus buttons at rest: on the borderless text/icon variants it draws a box FB never intended, and on the rest it repaints the library's own border. Restore Element Plus' variable first, then clear the borderless variants. Scoped to the embed and to the dialogs, drawers and popovers FB teleports to — the task modal (.el-overlay .fbs_view_task_modal) lives there, which is why it kept the black boxes. */ :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button { border-color: var(--el-button-border-color, transparent); } :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button.is-text, :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button.is-link, :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button--text, :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button.is-circle, :is(.fluent_boards_frontend, .el-overlay, .el-popper) .fbs_topbar_icon_btn, :is(.fluent_boards_frontend, .el-overlay, .el-popper) .fbs_task_modal_nav__btn, :is(.fluent_boards_frontend, .el-overlay, .el-popper) button[class*="close"], :is(.fluent_boards_frontend, .el-overlay, .el-popper) button.el-tooltip__trigger { border-color: transparent; } :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button:focus, :is(.fluent_boards_frontend, .el-overlay, .el-popper) .el-button:focus-visible { outline: none; } /* 2. Toolbar logo and menu alignment. The site header right above the embed already shows the WW logo, so inc/fluentboards.php strips

from the shortcode markup (do_shortcode_tag). The display:none below is only a guard in case FluentBoards changes that markup. With the logo gone, the Dashboard / Boards / Reports list starts at the left edge of the toolbar where the logo used to sit; 2.0.12 centres it (ul.fframe_menu {justify-content:center}, 1.32 had it left-aligned next to the logo). The off-canvas mobile menu is a separate list and is not affected. */ .fluent_boards_frontend.fbs_page_render .fframe_main-menu-items .menu_logo_holder { display: none; } .fluent_boards_frontend.fbs_page_render .fframe_main-menu-items ul.fframe_menu { justify-content: flex-start; } /* 3. Global search button: no border on hover/focus. The Elementor kit styles every