Add device-specific responsive visibility controls for blocks/patterns
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
Línea de trabajo
The payload names no files, tests or entry points, so the first step is finding where Raft defines its container and group blocks. The repository description says issues should be filed in Codeinwp/otter-blocks, so confirm with maintainers which project owns this before writing code. Done means a Desktop/Tablet/Mobile visibility toggle in the inspector that applies display: none through media queries in both the editor preview and the frontend.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Impact: 65 · Confidence: 90 · Complexity: 55
Description
Problem
Users cannot display different banner blocks or content patterns depending on screen size (e.g. desktop vs. mobile). Standard Gutenberg blocks in Raft render across all screen sizes without native options to hide or show specific sections on mobile or desktop.
Desired Behavior
Provide responsive visibility settings on theme container/group blocks or block patterns allowing site creators to toggle visibility per device breakpoint (Desktop, Tablet, Mobile).
Acceptance Criteria
- Include a 'Responsive / Visibility' panel in the block inspector for standard theme block containers.
- Allow users to toggle visibility settings independently for Desktop, Tablet, and Mobile screens.
- Ensure hidden blocks apply appropriate CSS rules (e.g.,
display: nonevia media queries) on target screen sizes in both editor preview and frontend.
Customer Context
Feedback entry 1 (active for 74 days, deactivated due to missing options): Customer needed to customize mobile view by serving specific banner variations per screen size, but found no built-in theme options to achieve responsive banner visibility.
Root Cause Analysis
The customer wants to present distinct banner layouts optimized separately for mobile and desktop screens. Standard Gutenberg FSE theme structures in Raft lack built-in responsive visibility toggles (hide on mobile / hide on desktop) for core block containers or patterns, requiring external plugins or custom CSS to achieve device-specific block rendering.
Reasoning
The user uninstalled Raft because they were unable to set up different banners for different screen sizes (specifically desktop vs mobile view). Raft is a standard FSE block theme relying on default Gutenberg block controls, which natively lack per-device display rules or responsive block visibility controls for hero banners. While block plugins like Otter provide section visibility conditions, Raft itself lacks native responsive display controls or device-specific block variation settings.
Source: automated uninstall feedback — raft, 2026-11-02
Generated by feature-request-triage workflow (ID: feature-request-triage_6ae96a93e3f317.68702671)
- Lenguaje dominante
- PHP
- Estrellas
- 8
- Forks
- 4
- Merge medio
- 7 h 18 min
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Codeinwp/raft
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
-
Mobile Menu Raft 1.1.5Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
-
Custom palette colors don't workAbiertobug customer report
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
-
Font sizes at Frontend vs EditorAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
Todos los issues de Codeinwp/raft
Issues similares
-
Change: check an identifier filter the same way in every tool - the order of somcp_search_ordersAbiertoconsistency enhancement Orders
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
novalo-dev/Prestashop-MCP-Server#343 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
claude
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
sprain/sprainocchio#45 ·
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día